[drupal-devel] Profiling memory consumption (was TCPHP goes for Drupal)

Matt Westgate matt at asitis.org
Wed Jun 1 13:54:10 UTC 2005

On Wednesday 01 June 2005 02:13 am, Dries Buytaert wrote:
> > http://www.asitis.org/tmp/drupal_load-memory.png
> How do I interpret that?  16.22% of all memory is allocated in
> drupal_load()?

Since that screenshot is sorted by the 'Self' column, it means 'the amount of 
memory taken by a function', so drupal_load() uses 16.22%.  

Looking at that chart again it would have been more meaningful to sort by the 
'Incl.' column which means 'the amount of memory of the overall lifecycle'. 
Then we can see that call_user_func_array(), node_page() and 
node_page_default() need to be analyzed instead and drupal_load() really 
doesn't seem to be a bottleneck. 

Of course I can't lay any claims to being an xdebug/kcachegrind expert and 
xdebug 2.0 beta may still be buggy.


More information about the drupal-devel mailing list