in reply to Re: Using Devel::Profile output to know what to do next
in thread Using Devel::Profile output to know what to do next

Hang on, cowboy. You need to profile first to see if that method is taking up any real time or not. Your work could be totally pointless if the lowercase calls don't take a significant part of the actual wall time.
  • Comment on Re^2: Using Devel::Profile output to know what to do next

Replies are listed 'Best First'.
Re^3: Using Devel::Profile output to know what to do next
by hv (Prior) on Jun 09, 2005 at 10:32 UTC

    Well whose two routines are taking 91 seconds of CPU time, so unless it's a multi-processor machine or a threaded application, they won't be taking less than 91 seconds of wall clock time.

    The numbers suggest total CPU time around 6.5 minutes; it would be useful to hear from the OP what the actual runtime is, but I'd expect my proposed hack to take more than a minute off it, replacing the 26+17 μs for 2.2 million calls with something more like the 10 μs of the accessor.

    But it is true - I'm used to profiling on a busy server, where useful wall clock times are hard-to-impossible to get, so mostly I concentrate on profiling to optimise CPU requirements, and use a combination of two other techniques for optimising the database side - the ever-popular "finger in the air" and "it hurts when I do this" techniques.

    Hugo