in reply to Profiling woes

Hmmm ... I would start with logging and timing before I jumped into any of the profile modules. That way I could narrow down the chunk(s) of code that are problematic. BTW ... I would use Benchmark's timediff method: 

my $t1 = Benchmark->new()
#
# chunk of code
#
my $t2 = Benchmark->new();
my $td = timediff( $t2, $t1 );
$log->debug( "Chunk x took " . timestr( $td ) );

[download]

-derby

Replies are listed 'Best First'.
Re^2: Profiling woes
by perrin (Chancellor) on Apr 09, 2008 at 12:55 UTC
    Theoretically, Devel::DProf should be a good way to find the parts of the program that need attention. It can tell which subs are taking up the time.
[reply]
Re^2: Profiling woes
by goupilInside (Sexton) on Apr 09, 2008 at 15:41 UTC

    That's my "plan B" if I can't make the profiler work.

    But I'd rather not touch too much code.

[reply]

In Section Seekers of Perl Wisdom