You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Dale Ghent <da...@elemental.org> on 2002/07/05 15:15:18 UTC

Re: cvs commit: httpd-2.0/server/mpm/worker mpm.h worker.c

On 4 Jul 2002 striker@apache.org wrote:

| striker     2002/07/04 08:20:54
|
|   Modified:    .        CHANGES
|                server   core.c mpm_common.c
|                server/mpm/beos beos.c mpm.h
|                server/mpm/experimental/leader leader.c mpm.h
|                server/mpm/experimental/threadpool mpm.h threadpool.c
|                server/mpm/netware mpm.h mpm_netware.c
|                server/mpm/prefork mpm.h prefork.c
|                server/mpm/worker mpm.h worker.c
|   Log:
|   Add a new directive: MaxMemFree.  MaxMemFree makes it possible
|   to configure the maximum amount of memory the allocators will
|   hold on to for reuse.  Anything over the MaxMemFree threshold
|   will be free()d.  This directive is usefull when uncommon large
|   peaks occur in memory usage.  It should _not_ be used to mask
|   defective modules' memory use.

Shouldnt this directive be more like "MaxMemAlloc"?

"MaxMemFree" makes me think of "The maximum amount of free memory on the
system" which this is clearly not it's intended setting... it's the
opposite.

/dale