dan at jumbuk.com
Tue Feb 10 04:02:24 PST 2009
Further to the recent talk (in part) on NYTProf by PauI I noticed that
for certain workloads NYTProf can add significant overheads. See
below. (Note that the process being profiled appeared to be CPU/Memory
bound.) It is not all bad. I have no idea how this overhead would
compare compare to other profiling options - except that the overhead
was much lower than attempting to find interesting (i.e. slow or
poorly written) parts of the code manually. In this case NYTProf made
it quite clear what part of the code was 'interesting'....it rocks!
[dan at localhost checkpatch]$ time perl ./checkpatch.pl --no-tree -q
[dan at localhost checkpatch]$ time perl -d:NYTProf ./checkpatch.pl
--no-tree --file aten2011.c
The discussion that prompted this is here:
If anyone is interested I can also post the HTML reports somewhere.
More information about the Melbourne-pm