> > Should be done now.
> 
> yep, i'm gonna test it.

i used trac to make stress test for the system. i send a lot of various
request to certain trac pages for cca 5 min and waited cca 10min to have all
pages showed in browser. in that time aussie load reached 24 https processes
(you can see the peak around t=2120).

after this peak it took the system aprox hour of time to get back to 8 httpd
processes and some reasonable load (0.3 in time i'm writing this).

during that one hour i watched apache logs and there was no extraordinary
traffic which could be responsible for such kind of load ranging between 10-20.
so i conclude this was needed just for (un)swapping purposes and cleaning
processes which finally lead back to low load and number of httpd processes.

this is _far_too_high_ and i suggest we should still go down with the number of
maxclients; there is no point in allowing 24 apaches when their only work is
swapping the whole box to death.

i have observed that 8 processes are able to qork on some 0.x load, so this is
the lower bound and i would say lets put the higher bound somewhere between
12-15.

pavel

Reply via email to