Could this be a keepalive issue? I think keepalive support was fiddled
with in recent mod_proxies.
R.
On Mon, 1 Jul 2002, E Kolve wrote:
> 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
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 mo
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 l
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
