in reply to Re^2: Optimizing a large project.
in thread Optimizing a large project.

We're measuring the response time between the timestamp of the event and when we responded to it.
So, that would be wall time. Profile with wall time then.
We do have fairly significant IO, both to disk and the network. The files are buffered writes, so we don't think that's our problem.
If you never measured it, you don't really know. I/O is nearly always the problem on modern hardware, unless you're doing 3D rendering or something similarly compute intensive.

Replies are listed 'Best First'.
Re^4: Optimizing a large project.
by dextius (Monk) on Jun 12, 2008 at 21:00 UTC
    I'll tackle the I/O benchmarks immediately, do you have a suggestion on a specific approach by chance?
[reply]
      I don't know how the NYT profiler does things, but with Devel::DProf all you have to do is take the data you already have and feed it to dprofpp -r. The -r flag means "real" time.

      UPDATE: Looks like NYTProf makes you declare this before you collect the profile data. The option is called "useclocktime".

[reply]

In Section Seekers of Perl Wisdom