In the year of Our Lord Tue, 6 Feb 2001 12:04:27 +0200, "Dirk Moolman"
<dirkm@reach.co.za> spake, saying:
>Hallo everyone, I'm not sure how to word this question.
>
>Regarding the oninit processes running on our machine, is it possible to
>see inside the process to see which users are causing the oninit to do so
>much work ?
>onstat -g ses will show how much memory a given process is grabbing.Sometimes
>that can help to identify naughty processes.
Thanks for the tip. There are so many onstat options, that one sometimes
forget some of them.
>One thing we do is to run "top" to identify the top processes on the
server.
>The oninit processes sit right on top - where they should be, but they
don't
>always do the same amount of work. If we have badly written code, it will
>still be the oninit doing all the work, so how do I trace the problem from
>the oninit back to the "bad program" / user ?
>Just pick one at random. Or all of them.
>All I see right now is a busy system and oninits doing alot of work. I
>would love to be able to drill down further and say to everyone, "here is
>the program slowing your system down".
>Do you see any of your.4gi's in the top pile?
That's one of my problems - I don't see the 4gi's at the top, this is why I
want to drill down into the oninits to see what's happening inside them.
onstat is probably the way to go, but I was wondering if there was another
tool to do this, similar to xtree ? But then we're probably looking at
dbamon, etc.
>I would say that we are at a point where we cannot add more resources to
the
>server, so we are now trying to identify bad programs, etc. to increase
>performance.
>------=_NextPart_000_0022_01C09034.F46039E0
>Content-Type: text/html;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
Please don't post MIME/HTML.