lients 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 <
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 downg
I got this error and spent a bit of time trying to figure it out. The
reason I was getting it was that I had started with a RedHat 7.2 system
which comes with Perl 5.6.0 and upgraded to 5.6.1 using RH 7.3 RPMS. I
then compiled mod_perl against 5.6.1. Each time I started up I got the
absurdfo
