[xdebug-general] Re: Time unaccounted for

On Mon, 2 Oct 2006, Marcus Bointon wrote:

> I'm trying to track down a major performance problem in a class using the
> profiler and kcachegrind. One method takes by far the longest, and it doesn't
> call any further functions, so I can't drill down any further. The source for
> this class is 73 lines, but when I view source in kcchegrind, I see that the
> biggest chunks of time occur in this class on lines 144 and 179, places that
> just don't exist (and they are displayed as blank lines with the time values
> next to them)! If I add up the time values for the actual function calls that
> are there in the source view, it comes to about 3, but these nonexistent lines
> add another 72, which is destroying my performance! Where is this extra time
> going? Where are these blank lines coming from?
>
> The code is in a tight loop, and I'm running from CLI for now, so the output
> files can get quite big (80M or so) if I let them - could I just be seeing
> xdebug overhead in writing the profile output?

HMm, interesting. The profiler only profiles on a function resolution so
it showing time for just two empty lines doesn't make much sense.
Without the code or profile file I can't really say what's going on
though.

regards,
derick

-- 
Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org