Mailing List Archive

> What other apache modules are needed to get mod_backhand to compile and
> function? Does it rely on any other apache modules? We want to build a
> mod_backhand server purely for proxying connections to other
> mod_backhand servers, and we want each httpd process to have the
> smallest memory footprint possible.

Is your mod_backhand box _only_ proxying? If so, then you can
strip pretty much everything out of it. If it's doing authentication,
then you'll need to spruce things up a bit... Have you compiled
everything as a DSO? If so, then just uncomment each (Load|Add)Module
directive out of your conf file and go from there... along the way
you'll find a few directives that start to break and will need to be
commented out/deleted. All and all, it's a good learning experience
because you'll see what directives come from what modules and you'll
know exactly what a minimal configuration is. -sc

--
Sean Chittenden

Yes, it will be purely proxying. If the servers behind the proxy do
authentication, will we really need this compiled on the proxy server?

Sean Chittenden wrote:
>
> > What other apache modules are needed to get mod_backhand to compile and
> > function? Does it rely on any other apache modules? We want to build a
> > mod_backhand server purely for proxying connections to other
> > mod_backhand servers, and we want each httpd process to have the
> > smallest memory footprint possible.
>
> Is your mod_backhand box _only_ proxying? If so, then you can
> strip pretty much everything out of it. If it's doing authentication,
> then you'll need to spruce things up a bit... Have you compiled
> everything as a DSO? If so, then just uncomment each (Load|Add)Module
> directive out of your conf file and go from there... along the way
> you'll find a few directives that start to break and will need to be
> commented out/deleted. All and all, it's a good learning experience
> because you'll see what directives come from what modules and you'll
> know exactly what a minimal configuration is. -sc
>
> --
> Sean Chittenden

--
Monte Ohrt <monte@ispi.net>
http://www.ispi.net/

> Yes, it will be purely proxying. If the servers behind the proxy do
> authentication, will we really need this compiled on the proxy server?

Not unless you decide to authenticate on the proxy servers,
which you arn't, so leave it out. Sounds like you only need
mod_backhand... do you need mod_rewrite? It might be good to push that
off to the proxy servers that way you take as little CPU as possible on
the backend servers. -sc

--
Sean Chittenden

On Monday, September 10, 2001, at 03:58 PM, Monte Ohrt wrote:
> Yes, it will be purely proxying. If the servers behind the proxy do
> authentication, will we really need this compiled on the proxy server?

To drop some pennies into the idea bucket. If you are running in
proxying only mode, you will have a multitude of connections from very
few front-ends to very many back-ends. Though I think connection
pooling is super cool, I think that you could gain considerably by
disabling it (available in the CVS version). This allows you to run
with 2048 max clients without a problem and the individual children
don't want on a single moderator process (I find this hurts under heavy
load).

So, try the CVS version and disable connection pooling and you may see
some benefit. I have connection pooling on in small installations and
off in large installations.

--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7