Perrin Harkins wrote: [...]
It seems that to tune properly you would need to send in requests with a benchmarking tool and keep adjusting MaxClients upward while watching the free memory on the box. That's really ugly. Maybe there's a way to count memory used by each process slowly but accurately which we could use during tuning at least.
that approach is not very practical if change your code base constantly. Since you will have to retune things every time you change your code.
I'd rather see the kernel providing a new feature which tells us the exact amount of memory used by a group of forked processes (swapped in and out). If we have this number we are gold. just maintain a table of absolute process sizes and kill the biggest processes, when that total memory usage number is bigger than the limit. i.e. limiting all procs at once, rather on the process by process basis. So this will still provide a solid protection from swapping.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
