Re^3: Benchmark.pm ing -- and a little confused

Yes, if the code of interest is being run on a remote machine, then wallclock seconds are your best measure.

Caution: Contents may have been coded under pressure.

Comment on Re^3: Benchmark.pm ing -- and a little confused

Replies are listed 'Best First'.
Re^4: Benchmark.pm ing -- and a little confused by halley (Prior) on Mar 15, 2005 at 17:40 UTC
Just remember, if the wallclock time is significantly affected by things unrelated to the actual CPU time spent running your script, then your script isn't necessarily the bottleneck, and may not be your prime target for any optimization work you've been planning. -- `[ e d @ h a l l e y . c c ]`	[reply]