I was watching the apache scoreboard file and it appeared the the mod_perl process was not being immediately freed by the proxy. Normally there will be 3 or 4 mod_perl procs in mode "W" Sending Reply, but after around 20 - 30 seconds on 1.3.26 as the proxy all 30 (that is my MaxClients for mod_perl) were in "W". This seems like a problem with either the IOBufferSize that was recently added or possibly something to do with the proxy not releasing the mod_perl process once it has gotten the last byte...
--eric David Dyer-Bennet wrote: > E Kolve <[EMAIL PROTECTED]> writes: > > >>Has anyone noticed any performance problems using 1.3.26 as the front >>end proxy to a backend mod_perl server? >> >>I upgraded a box running apache 1.3.22 as the frontend proxy to >>1.3.26. Prior to upgrading the load was ~2.0 - 3.0. After upgrading, >>the load went up to around 21 - 25. I then downgraded and the load >>went back to normal. Could this have anything to do with the changes >>to mod_proxy between 1.3.22 and 1.3.26? Any ideas? > > > You don't actually talk about any performance problem. Were the > proxied requests in fact running slowly? It seems to me a difference > in the process structure or what how they wait could have horrible > effects on the load average numbers while actually improving > performance. Or not.
