Re: Perl code timing

I'm not sure what your client is looking for. Does the client want to know if your code is faster than something else? If the code is fast enough, than it's fast enough. (Sometimes phrasing something that simple is what it takes to convince people).

Other options:

Devel::Dprof
Devel::Profile (I like this module. Easy to use and it doesn't segfault)
Devel::Profiler (A replacement for Devel::Dprof)
Ask the client what number he or she wants, write it down on a piece of paper and hand it back.

Cheers,
Ovid

New address of my CGI Course.

Comment on Re: Perl code timing

Replies are listed 'Best First'.
Re: Re: Perl code timing by tbone (Beadle) on Oct 31, 2003 at 18:45 UTC
Take a look at the Benchmark module	[reply]
Re(3): Perl code timing by Ovid (Cardinal) on Oct 31, 2003 at 18:55 UTC
Feh. Lately I've been doing so much work with profiling that I forgot an obvious answer :) Cheers, Ovid New address of my CGI Course.	[reply]
Re: Re: Perl code timing by mcogan1966 (Monk) on Oct 31, 2003 at 19:37 UTC
Nothing all that complicated really. It's more bureauocratic ca-ca than anything else. But they would like to see that I ran some kind of 'metric' and kluged some data together to show that the code itself is reasonably well written and efficient. I can make the data do what I want it to do, I'm just looking for some way to get some data that I can use in this case. There will be a comparison to a previous 'version' of what I'm now writing. But that version was written by $someone_else, and therefore not much my concern. What I've written runs a touch slower, but provides significanly better results. And it's the better results that needs the bigger play. I just need to show some kind of numbers on the relative speed of both programs. If need be, I can outright 'fudge' numbers with a stopwatch. I'm just looking for something technical enough that I can make a manger's eyes glaze over. :)	[reply]