[xdebug-general] Re: Cachegrind format

From: Derick Rethans <derick[@]xdebug.org>
Date: Sun, 1 Mar 2009 13:21:51 +0000 (GMT)

On Thu, 19 Feb 2009, Tom Walter wrote:

> A couple of questions about cachegrind files.
> I get the impression that the xdebug cachegrind files cannot show memory
> information, although I've never seen anyone outright say that. Why is this,
> and is it something that is planned to be fixed?

The way how cachegrind handles aggregation doesn't work well with how
memory profiling works unfortunately.

> Also exactly what are the numbers in the cachegrind files? The 'events' header
> of the cachegrind file labels them 'Time', but this doesn't tell me much, they
> are not milliseconds, perhaps they are clock ticks? But if so, why doesn't the
> header say 'ticks'.

They're microseconds, if I recall correctly.

> I use wincachegrind and that interprets them as milliseconds, but that
> doesn't seem right at all, because if I try and correlate the times
> with the data output in an xdebug trace file, it doesn't match up at
> all.

Remember that the profiler tries not to include information about the
time that it takes PHP to call a specific function — so this could be a
point of difference.


Like Xdebug? Send a postcard: http://derickrethans.nl/xdebug_2_released.php
Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org
twitter: derickrethans
Received on Sun Mar 01 2009 - 14:21:46 GMT

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST