If you have found out anything else, I would very much like to know
about it.
i read your posts with hongli and those are similar but different. since
i simply couldnt get the reliability i needed with the proc tweaks etc.
i just upgraded the box(es) to a quad core with more ram and that seems
to have solved at least the
./ab -c 100 -n 1000 http://192.168.1.53
problem...for now.
interestingly, i came across this post last week or so :
http://poocs.net/2006/3/27/the-adventures-of-scaling-stage-3
and towards the end there this quote :
"Using tcpdump to monitor the traffic on the listener ports showed..
nothing. Not a single byte crossing the line. Using strace to check what
the “stuck” listener is busy doing showed it sitting there in
“Waiting..” state. Also doing nothing.
Now the stunning part: If you restart lighttpd or the dispatcher things
start working again. In the end, this didn’t indicate either side as
being responsible for the hang and we started looking elsewhere."
which is exactly the problem im having but completely architecturally
different and two years later. bizarre.
they also started meddling around in proc except their changes had
little to no effect from the sounds of things.
i knew about that mpm-prefork sorta, but since the default apache
install seemed to work, i havent yet concerned myself with it.
is there a release date for 1.1? im on 1.0.5, but havent been able to
reproduce the strange hanging which i assume is because of the quad core
actually, three quad core machines load balanced.
ill have more information available next month when we begin serious
load testing. were going live in august from java to rails and our site
is 125,000+ page views per day. the money is on passenger for now, but a
last second move to mongrel may be inevitable
well see
..