jwr@scotty.UUCP (06/09/88)
References: We are interested in help and/or recommendations pertaining to software performance monitoring tools. Our knowledge and experience in this arena is limited. One of our desired goals is to have the capability of determining the overhead (processing time) associated with the various modules of code to identify what processes are consuming the greatest amount of execution time. Our initial attempt used the system time function and we have found it to be insufficient. It may partly be due to not totally understanding the terminology associated with the time function. We are presently using SUN 3 machines running SUN UNIX 4.2 release 3.5. Any help or advice in this area would be greatly appreciated. Thanks!
bitbug@vsi1.UUCP (James Buster) (06/10/88)
Check out the prof(1), and gprof(1) manuals, as well as the -p and -pg options
of cc(1). That should give you what you want. I use gprof(1) personally.
--------------------------------------------
James Buster
Mad Hacker Extraordinaire
...!{sun,decwrl}!pyramid!vsi1!bitbug
--------------------------------------------dwc@homxc.UUCP (Malaclypse the Elder) (06/14/88)
> Check out the prof(1), and gprof(1) manuals, as well as the -p and -pg options > of cc(1). That should give you what you want. I use gprof(1) personally. > see "inaccuracies in program profilers" by carl ponder and richard fateman in software practice and experience, may 1988 to read about the limitations of sampling based program profilers. we are presenting a paper in the upcoming usenix conference on a new tool that actually measures the elapsed time spent in a function rather than using a sampling method. the paper is titled "CASPER the friendly daemon". danny chen ihnp4!homxc!dwc