Re: Re: PHP profiling results under 2.0.37 Re: Performance of Apache 2.0 Filter
| From: | Zeev Suraski | Date: | Sun, 09 Jun 2002 00:09:24 +0000 |
| Subject: | Re: Re: PHP profiling results under 2.0.37 Re: Performance of Apache 2.0 Filter | ||
| References: | 1 2 3 4 5 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-85055@lists.php.net to get a copy of this message | ||
At 02:57 AM 6/9/2002, Brian Pane wrote:
In the httpd, we've done two things to minimize the fragmentation: * Memory for these heaps is almost always allocated in chunks of a fixed size, 8KB.Hmm, but doesn't that mean that the largest contiguous block this heap will be able to provide is 8KB, then?
* There's a two-layer structure to the heaps:
- apr_pool objects are what the application uses. Each pool
provides a fast alloc interface, no free function, and a
"destructor" that returns all the allocated space when the
pool is destroyed.
This is probably not very suitable for PHP. We allocate and free *a lot*, not being able to free is going to increase memory consumption significantly. If we use APR heaps, are we bound by this behavior?
Zeev