On 10 Nov 2011, at 11:12 PM, Stefan Fritsch wrote:
I intend to set MaxMemFree by default. The reason is that some
modules use a lot of memory for a few requests (e.g. mod_dav,
mod_php). With MaxMemFree disabled, the allocators will grow to the
size necessary to serve the most memory
On 11/10/2011 3:12 PM, Stefan Fritsch wrote:
Hi,
I intend to set MaxMemFree by default. The reason is that some modules use a
lot of memory
for a few requests (e.g. mod_dav, mod_php). With MaxMemFree disabled, the
allocators will
grow to the size necessary to serve the most memory intensive
On Thu, Nov 10, 2011 at 4:12 PM, Stefan Fritsch s...@sfritsch.de wrote:
Hi,
I intend to set MaxMemFree by default.
+1.
What about a way to view allocator memory use? per child totals in
mod_status would be most excellent.
Greg
On Fri, 11 Nov 2011, Greg Ames wrote:
I intend to set MaxMemFree by default.
+1.
What about a way to view allocator memory use? per child totals in
mod_status would be most excellent.
Sure. We should try to put the necessary infrastructure into apr 1.5 and
then support it in mod_status
On Fri, 11 Nov 2011, William A. Rowe Jr. wrote:
I think 4MB could be a reasonable default for MaxMemFree.
Were you considering that in terms of a 64 or 32 bit arch? Guessing
that from alignment and ptr sizes, there will be some impact.
I didn't intend to handle that differently.
We
Hi,
I intend to set MaxMemFree by default. The reason is that some modules use
a lot of memory for a few requests (e.g. mod_dav, mod_php). With
MaxMemFree disabled, the allocators will grow to the size
necessary to serve the most memory intensive type of request and never
shrink again. And
