in reply to Re^2: Benchmarking A DB-Intensive Script
in thread Benchmarking A DB-Intensive Script

Take a look at Benchmark::Timer. You can wrap a start/stop pairing around a piece of code and it accumulates the iterations and average the times taken for you. You can also run several different and overlapping pairs concurrently, which makes it easy to start with a course granularity and then home in onto those parts where you need finer granularity.

It allows you to get finer granularity than one of the per subroutine profilers without resorting to the time expensive per line profilers.

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.
  • Comment on Re^3: Benchmarking A DB-Intensive Script

In Section Seekers of Perl Wisdom