Hello Scott,
Many many thanks for your guidance. I followed the binary search among
modules and was quickly able to pinpoint mod_cband (
http://sourceforge.net/projects/cband/) as the reason of why the number of
shared memory segments keeps increasing.
Again, many thanks to you and everyone who h
"Chandranshu ." writes:
> We changed our script that used to do a graceful restart to also
> record the number of shared memory segments before and after the
> restart. Plotting the number of shm segments vs. the number of times
> the server was restarted gracefully was almost a straight line.
H
Chandranshu . wrote:
Hi André
Our server is handling around 20 requests per second. Please note that this
is not a single site. There are many sites that are hosted on this server.
As requests to host new site keep coming in, we keep reloading the virtual
host config through a graceful restart.
Hi André
Our server is handling around 20 requests per second. Please note that this
is not a single site. There are many sites that are hosted on this server.
As requests to host new site keep coming in, we keep reloading the virtual
host config through a graceful restart.
Here are my KeepAlive
Chandranshu . wrote:
...
Just to help in getting an idea of your site :
- how many requests is your site typically handling (per second, per
minute..) ?
- what is your KeepAlive setting ?
and, why did you change the default for MaxRequestsPerChild ?
any particular reason, or just for the sake o
Hi
We changed our script that used to do a graceful restart to also record the
number of shared memory segments before and after the restart. Plotting the
number of shm segments vs. the number of times the server was restarted
gracefully was almost a straight line.
Even doing a `apachectl -k rest
