 |
 |
 |
|
While the posted version continues to be updated, this is the first and original Oracle Response Time Analysis paper, which was published by Mr. Shallahamer in 2001.
Abstract
Early Oracle performance tuning practitioners used a large number of performance ratios to help optimize their databases. In the mid-1990's session wait event analysis was born allowing direct Oracle contention identification. The next performance analysis frontier is response time analysis. Response time analysis focuses on quantitatively understanding performance pain.
Yes there is always a performance bottleneck. But sometimes we don't care because performance is OK. What is missing from both Ratio Based and Wait Event Based analysis is quantifying user irritation and it components. Oracle response time analysis enables response time measurement, bottleneck validation, user irritation quantification, and improved tuning focus. Therefore, response time analysis is absolutely key to fully and efficiently optimize Oracle based systems.
There have been many challenges with measuring Oracle response time and its components. For example, Oracle makes no distinction between a database transaction and a business transaction, response time definitions are perspective based, lack of wait event instrumentation, and Oracle's poor operating system resource instrumentation facilities. However, even with these challenges, response time analysis can be performed. In fact, response time and its components can be accurately calculated at the system and the session level and using only data from Oracle's virtual performance views.
This paper is all about understanding, using, and taking advantage of the next Oracle performance management frontier; response time analysis. |
|
|
|
|
|
|
