Yes, the proxy is an option 10x for the advice. I already started playing with the max number of processes and the size and I'm interested what are your optimal settings.
But why is this problem? I can't see what will cause 40M additional memory to be taken per process. I'm using Slackware 8.0 with 512M of RAM. ----- Original Message ----- From: Marco Marongiu Cc: axkit-users+AEA-axkit.org Sent: Tuesday, May 28, 2002 10:56 AM Subject: Re: Huge httpd processes Pavel Penchev wrote: +AD4- +AD4- At start time the size is about 6M. After opening each page of the site the size reaches about 11M and after that continues to grow. +AD4- It grows at some requests and and doesn't at others. It happened to me, too. In fact I had to do some fine tuning to balance the maximum number of processes to spawn and the maximum size for each. To keep the situation in control, I put an Apache proxy in front of AxKit, sharing the same DocumentRoot-s, and used mod+AF8-rewrite. This way, a small Apache process (the proxy) serves the static pages and redirects and caches requests for dynamic pages. I'm using it on a Debian Linux +ACI-Woody+ACI- with 128Mb RAM, it's up 38 days and it still haven't touched the swap. Ciao marco -- Marco Marongiu Email: bronto+AEA-crs4.it CRS4 Research Center Phone: 070 2796 336 NCS Division Fax: 070 2796 216 NSM Group WWW: http://bugs.unica.it:4444/ --------------------------------------------------------------------- To unsubscribe, e-mail: axkit-users-unsubscribe+AEA-axkit.org For additional commands, e-mail: axkit-users-help+AEA-axkit.org
