in reply to Gathering data on Profiling woes

Back when I was working on Devel::Profiler I had a hard time profiling the following modules: 

UNIVERSAL Time::HiRes B Carp Exporter                                 
+      
Cwd Config CORE DynaLoader XSLoader
AutoLoader

[download]

That's the default bad_pkgs setting which skips trying to instrument subs in those modules.

If you haven't decided which profiler to fix, please consider fixing Devel::DProf. If that module worked better the rest would be largely unnecessary. Failing that, you might consider working on Devel::Profiler, which was created as a last resort when I failed to fix Devel::DProf to work on Bricolage.

-sam

Replies are listed 'Best First'.
Re^2: Gathering data on Profiling woes
by BrowserUk (Patriarch) on Nov 01, 2005 at 22:59 UTC

    FWIW: If there is going to be a thoroughly revamped profiler, I'd prefer it to something like Devel::SmallProf. It's line-by-line granularity seems considerably more useful to me.

    I also like it's ability to control what gets profiled through the inclusion of in-line directives (global assignments.

    The downsides are that it is rather slower than some other profilers and doesn't work with or have the equivalent of dprofpp. That said, it's native output format is emminently usable, and easily manipulated with an editor, Perl or most other text-based tools like grep etc.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom