Common Performance Ideas/ Considerations

From OraWiki

Jump to: navigation, search

This is a lousely coupled set of ideas related to performance.


[edit]

Sequence Diagrams


Creation of a Sequence Diagram, the distribution of response time over components of the performance stack, is sometimes difficult.

An indirect way to create such an information seems to be the before/after measurement. For example get information of the response time of a transaction. After you've gathered valid data change parts of the performance stack and measure the difference at transaction level. Now you will be able to weight the percentage of the changed component in the whole performance stack.

Remember: Performance stack is defined as all components having response times. For example:

  • Hard Disk
  • Fibre Channel
  • Database Server (CPU's, Network, Instance config, Data Model, Cache efficiency, Index efficiency etc. pp.)
  • Network
  • Application Server (if there is one, coding of application server and all performance relevant parts of this component)
  • Network
  • Client Application (coding of transaction)


To get valid information of the changes at database level STATSPACK seems to be an excellent tool to gather such information if you use an Oracle Database.

Retrieved from "http://www.oraforecast.com/orawiki/index.php/Common_Performance_Ideas/_Considerations"
Personal tools