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

It looks like you picked the wrong profiler. You should use either Devel::DProf or Devel::Profiler, not Devel::Profile. The problem with Devel::Profile is that it measure the CPU time, not the "real" time that has elapsed. Waiting hours for a database query might not take much CPU time at all. If you use a profiler like the two I mentioned which lets you sort by wall ("wall clock" or real time), you will see how much time was really spent waiting for your queries to execute.
  • Comment on Re^3: Using Devel::Profile output to know what to do next

Replies are listed 'Best First'.
Re^4: Using Devel::Profile output to know what to do next
by Anonymous Monk on Jun 18, 2008 at 19:35 UTC
    no, Devel::Profile measures wall time, not cpu time.