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 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
