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

[Dries Buytaert]

On 28 May 2005, at 17:46, Matt Westgate wrote:
>> I have been thinking about profiling Drupal's memory consumption.
>> I'd like know where most memory is consumed.  Is there an easy way to
>> profile this?
>>
>
> I used Xdebug 2.0 (beta) [1] and KCachegrind to profile the path  
> aliasing
> patch a couple weeks back. Xdebug outputs a ' Callgrind Profile  
> Format' file
> which can be read into programs like KCachegrind [2] or  
> WinCacheGrind [3].
> It allowed me to see memory usage and the time spent in functions.   
> The
> memory footprint in HEAD is already smaller than 4.6 since we got  
> rid of
> storing all aliases in a static variable.
>
> I ran a quick profile on a 4.6 site (with no aliases) and it seems  
> the next
> place to focus on would be drupal_load() in terms on memory usage.
>
> http://www.asitis.org/tmp/drupal_load-memory.png

How do I interpret that?  16.22% of all memory is allocated in  
drupal_load()?

--
Dries Buytaert  ::  http://www.buytaert.net/