Comments on: Finding the reasons for excessive logical IOs

By: Tanel Poder

Tanel Poder — Fri, 25 Dec 2009 05:19:33 +0000

Jonathan Lewis has also written about this topic:

http://www.jlcomp.demon.co.uk/buffer_usage.html

By: Tanel Poder

Tanel Poder — Fri, 25 Dec 2009 05:09:02 +0000

Well, I guess you have to read through it once more then!

What I have highlighted in the output is section with *BUFG*.

And earlier in the note I have documented that BUFG means “Buffer get reasons”.

If you’re doing too many buffer gets, you want to know WHY. And the reasons section will tell you that. For example this approach has allowed me to diagnose a problem with ASSM space allocation code in kernel, where majority of buffer get reasons started with KTS and for most of these the reason was reported as ktspscan_bmb in BUFG output).

By: willem

willem — Thu, 24 Dec 2009 22:10:56 +0000

Long output, yes. I don’t get the point though. How to know if the output points to a problem?

By: Hans-Peter

Hans-Peter — Thu, 03 Dec 2009 07:34:45 +0000

Hi Tanel,

Nice stuff!
I look forward for the follow up.

Regards Hans-Peter

By: Blogroll Report 13/11/2009-20/11/2009 « Coskan’s Approach to Oracle

Blogroll Report 13/11/2009-20/11/2009 « Coskan’s Approach to Oracle — Mon, 23 Nov 2009 01:59:19 +0000

[...] 17-How to find reasons excessive LIO? Tanel Poder-Finding the reasons for excessive logical IOs [...]

By: Haris

Haris — Fri, 20 Nov 2009 08:44:13 +0000

Hi Tanel

Very informative.

By the way, can you please give some interpretation the important point from the output and where actually the problem which caused the excessive logical IOs.

Thanks in Advance.

Cheers!

By: Tanel Poder

Tanel Poder — Fri, 20 Nov 2009 04:16:43 +0000

Thanks!

By the way I fixed a typo – kill -STOP suspends the process (not kill -SUSP as I wrote earlier)…

By: Dion Cho

Dion Cho — Fri, 20 Nov 2009 03:06:34 +0000

Tanel.

Good stuff as always. This would be a good example on how a simple question turns out to be a big knowledge.