Relate I/O's activity to processes

[Spendius]

Hi,

The guy here
http://rootshell.be/~yong321/freeware/pio1_3_c.txt
wrote a small C prg that easily allows you to see what
processes perform strong I/O's, and to further troubleshoot
eventual waits caused by this process activity. It's helped
me in a few cases to point out database problems.

But this code is only relevant to Solaris operating system:
I'd like to know if you could help me to adapt it to AIX
operating system.
As you'll see this code rests upon the psinfo files located
in /proc/<PID> directories. Is there a similar (and simple
too) way to get at processes I/O activity within these 3
operating systems as well ?

Thanks a lot !

[Nicholas Buckley]

Hi,

Thanks for the head up - this looks very useful.

Hang on though, AIX 5 now has a /proc of its own.

What exactly doesn't work when you try to compile / run this on AIX ?

I'll certainly be giving it a go myself, and will post my findings or any
AIX-specific modifications that I find necessary.

But it would be a shame to get tangled up in any issues that you may already
have identified ( or even fixed ).

Cheers,

Nick,
UK

"Spendius" <spen...@muchomail.com> wrote in message
news:1162977887.4...@i42g2000cwa.googlegroups.com...

[Mark Taylor]

> > http://rootshell.be/~yong321/freeware/pio1_3_c.txt
> > wrote a small C prg that easily allows you to see what
> > processes perform strong I/O's, and to further troubleshoot
> > eventual waits caused by this process activity. It's helped
> > me in a few cases to point out database problems.

download nmon, fire it up and hit "t" for top processes then "5" to
order by i/o throughput.

Or, run filemon ..

Or, Run a kernel trace and look for kreads and kwrites with high return
times.

No need to port some Solaris code really ..

Rgds
Mark Taylor

[Nicholas Buckley]

Some very fair points there Mark,

Still, who doesn't like a bit of recreational C-programming ;-)

Nick

[No Body]

"Mark Taylor" <m...@talk21.com> wrote in message > download nmon, fire it up

and hit "t" for top processes then "5" to
> order by i/o throughput.
> Or, run filemon ..
> Or, Run a kernel trace and look for kreads and kwrites with high return
> times.

.. or figure out wlm and fire it up in passive mode.

-r