On 9/13/05, Marcos R. Cardoso <mcardoso@xxxxxxx> wrote: > Hi, here where I work we have the following configuration for our web > server: > > Windows 2003 > Apache 2.0.54 > PHP 4.4.0 > MySQL 4.0.20 > Unfortunately we are experiencing some huge problems concerning memory > usage by the Apache child process: after 8 hours since the Apache > service has started, the child process has already allocated about 300 > Mb from the server memory, being necessary a restart for this process > otherwise the service fails. > > The solution I've found so far is to schedule restarts for the Apache > service every 8 hours, but I'd like to know if there is a proper > solution for this behaviour. The most likely explanation is a misbehaving php script. But to debug, you really need to work out what requests are triggering the ballooning memory requirements. I'm not very familiar with debugging this type of problem for win32, but if you can track threadid and memory over time, then you can add the thread id to the access.log and try to figure out what requests trigger the memory problems. You can also try setting MaxRequestsPerChild to a high but not infinite number to trigger automatic restarts that should clear things out. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|