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.
In reply to Re^3: Benchmarking A DB-Intensive Script
by BrowserUk
in thread Benchmarking A DB-Intensive Script
by bernanke01
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |