httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: AW: [Fwd: Re: Apache 2.2.3 mod_proxy issue]
Date Tue, 31 Oct 2006 16:56:39 GMT
=?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VF_EITO?= wrote:
> > Von: Jim Jagielski=20
> > Gesendet: Dienstag, 31. Oktober 2006 17:05
> > An: dev@httpd.apache.org
> > Betreff: Re: AW: [Fwd: Re: Apache 2.2.3 mod_proxy issue]
> >=20
> >=20
> > >=20
> > > I am a regexp fan and have mod_rewrite loaded in any of our=20
> > servers =3D
> > > anyway
> > > for some standard tasks, so this actually does not bother me :-).
> >=20
> > My "concern" is that the proxy-selection and operation should be
> > fast, as fast a possible, and mod_rewrite simply isn't the fastest
> > puppy in the world. Avoiding full-blown regex in ProxyPass allows
> > for nice pattern matching (globbing) without the overhead of
> > a full regex engine... fast fast fast should be the name of
> > the game.
> 
> That depends on the usage of the proxy. In the example given we talk =
> about
> a connection to a jsp in the backend. I am pretty sure that =
> mod_rewrite's
> part on the total response time / resource consumption (CPU / memory) =
> here
> is fairly low. So honestly, this is not my concern here.
> 

Well, it's mine and it should be anyone's really. After all,
we are not talking about the "extra" time taken in the request/
response phase but rather the switch-time taken for Apache
to determine when/if to proxy and where. Total req-per-sec,
not round trip time.

-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
	    "If you can dodge a wrench, you can dodge a ball."

Mime
View raw message