Oracle Performance Firefighting
by Craig Shallahamer

Get the book here



Craig Shallahamer's Blog

You were brought to this page based on an internet search and as a free service to Oracle DBAs.

The text below is an except from the book, Oracle Performance Firefighting, written by Craig Shallahamer of OraPub, Inc. Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click here.


©2009, 2010 by Craig Shallahamer. This is copyrighted material.
Please—Out of respect for those involved in the creation of the book and also for their familes, we ask you to respect the copyright both in intent and deed. Thank you.

-------------------------------

When additional or faster CPUs or IO devices are added to a system, we have effectively increased capacity. For example, because the old CPUs were replaced with CPUs that are twice as fast, instead of a SQL statement consuming 4 seconds of CPU, it now consumes only 2 seconds of CPU. Or perhaps six additional CPU cores were added. Thinking about the basic utilization formula of requirements divided by capacity, if capacity increases and the requirements remain the same, then the utilization must decrease. The only way to increase the utilization is to increase the requirements. One way to do this is to increase the workload (the arrival rate). So, by increasing capacity, we have provided the basic performance-enhancing options of decreased response time, increased throughput, or some combination of both.

From a queuing theory perspective, what really happens when capacity is added depends on if additional transaction processors (think more CPU cores) are implemented or the transaction processors are faster (think faster CPUs)-or if we're lucky, both. If the transaction processors are faster, the service time decreases with the same effect as with tuning. We can expect a new response time curve similar to the one shown in Figure 9-17 to take effect. However, if we add transaction processors with no change to service time, the response-time curve does not shift down. But because there are more transaction processors available, as a whole, they can process more transactions per unit of time, which shifts the curve to the right, allowing for an increase in the arrival rate before queuing sets in.

Figure 9-18 graphically shows how adding more transaction processors can affect a system. If the bottleneck is IO, then the same general effect occurs when adding IO devices. Starting at point A, the performance is unacceptable and highly variable. By implementing addition transaction processors, the response time decreases (that is, improves), and the system is operating at point B. However, now the administrators have a choice. By controlling the workload (the arrival rate), they can allow more work to flow through the system without affecting response time. Point C shows this negligible effect on response time by allowing the arrival rate to increase. So, by adding more capacity (either more and/or faster transaction processors), the performance analyst once again has several options: decreased response time, increased workload, or a managed combination of both.

©2009, 2010 by Craig Shallahamer. This is copyrighted material.
Please—Out of respect for those involved in the creation of the book and also for their familes, we ask you to respect the copyright both in intent and deed. Thank you.


Know what's important before it's too late!

OraPub's
Performance Training

is like no other...





More Class Pics...
Get student testimonials!