|
|
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. ------------------------------- It's simple to monitor latches. One way to do this is look at the latch requests (gets). If the latch is being requested, then you know it's active. Figure 7-18 shows an example taken from a small Linux server with a single CPU core and 200 processes defined. Notice the about 8.25:1 process-to-latch ratio is in effect. Figure 7-18. While 24 IMU latches have been created, at the time of this report, only 9 of them have been used, as evidenced by their gets activity. Identifying IMU latch contention is no different than identifying any other type of latch contention. If you're not comfortable with this, please review Chapter 3. 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!