in reply to Checking Perl script on server
Typically, as a system administrator, you want to monitor as much as possible. And what you are looking for are things that are unusual. For a particular program, you first have to get an indication of what you expect of the program, and what it's actually doing. For a program that does a lot of find and replace actions, you'd expect a lot of physical reads (unless most of the filesystem is already buffered), lots of logical reads, lots of logical writes, and depending on your filesystem and buffer size, physical writes.
90 to 95% CPU time could indicate many things. It could be that most of the files acted on are already buffered (hence little physical I/O, and no I/O waits). It could also mean that your program is written very inefficiently.
There's just too little information to say much about this situation.
As for tools, there's top, or its Solaris nephew prstat. You already mentioned it. You also mentioned truss, vmstat and ps. Good choices, and check out the manual page of truss, it has some useful options; counts of system calls can be very informative. HP has glance for HP-UX, which is, IMO, a wonderful tool. I think it has been ported to Solaris, but I'm not sure. However, if it is, it won't be free.
Abigail
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: Checking Perl script on server
by waswas-fng (Curate) on Jul 30, 2003 at 13:55 UTC | |
by Anonymous Monk on Jul 30, 2003 at 15:02 UTC | |
by snax (Hermit) on Jul 30, 2003 at 16:01 UTC | |
by smalhotra (Scribe) on Jul 30, 2003 at 16:28 UTC | |
by waswas-fng (Curate) on Jul 30, 2003 at 22:14 UTC |