Hi, and happy new year!
My modperl/mysql setup does not degrade gracefully when reaching
and pushing maximum pages per second :-) if you could plot
throughput, it rises to ceiling, then collapses to half or less,
then slowly recovers .. rinse and repeat.. during the collapses,
nobody but real patient people are getting anything.. most page
production is wasted: goes from modperl-->modproxy-->/dev/null
I know exactly why .. it is because of a long virtual
"request queue" enabled by the front end .. people "leave the
queue" but their requests do not.. pressing STOP on the browser
does not seem to signal mod_proxy to cancel its pending request,
or modperl, to cancel its work, if it has started.. (in fact if
things get real bad, you can even find much of your backend stuck
in a "R" state waiting for the Apache timeout variable
to tick down to zero..)
Any thoughts on solving this? Am I wrong in wishing that STOP
would function through all the layers?
thanks
-Justin
