NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Sun did the hard sums (Score:2)
To be fair Sun did all the heavy lifting. They added a quick "is this probe enabled" test that can be used to wrap the instrumentation code. In fact I'm told they developed it specifically to make dtrace fast enough for Perl! And it is fast. The benchmark figures there are for 10,000,000 calls to an empty subroutine - so if there was any performance hit to entry/exit it'd show.
Right now I'm working on getting Configure to handle dtrace. It's slightly complicated by the fact that Sun's /usr/sbin/dtrace and Apple's /usr/sbin/dtrace no longer have the same command line interface. Once that's done we'll get a patch into blead
Of course, we can instrument other things apart from subroutine entry / exit. Which other events in the interpreter are people interested in monitoring? We don't need to cover anything that causes a system call - because dtrace already does that.
Reply to This
Re: (Score:1)