|
|
by Craig Shallahamer Get the book here |
|
|
Craig Shallahamer's Blog
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. ------------------------------- With great anticipation, the product was repeatedly run, and the instrumentation report was generated. As shown in Figure 2-4, developer C was correct-the vast majority of her module's time was spent waiting for IO read requests to complete. Feeling vindicated, developer C went so far as to say that the development manager should have a talk with developer A, since his code was actually burning more CPU than anyone else's code! Figure 2-4. Sample instrumentation analysis code and the actual results. After repeated product runs, clearly module C must wait for IO reads to complete. The development manager quickly realized that he could also summarize the instrumentation by the resource, not only by the module. As shown in Figure 2-5, the development manager was clearly able to see that both IO reads and CPU consumption have a dramatic effect on the overall application performance. 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!