|
I see. Pls excuse my ignorance - I'm new to all this :-)
Hmm. I wonder how this TCP port issue directly limits the Zeus software load
balancer's incoming connection rate. In section 1.4 of
http://support.zeus.com/doc/zlb/sizing_guide.pdf, they describe this
problem.
Could it be because their balancer actually acts as a HTTP reverse proxy,
accepting all connections and then having to actually act as a client to the
real servers? I guess that must be it -- since their brochure at
http://www.zeus.com/library/products/zlb/zlb_brochure.pdf indicates that
they automatically translate HTTP 1.0 requests into HTTP 1.1 pipelined
connections.
To rephrase: A load balancer that operates on Layer 7 and maintains
persistent connections to the real servers has to act as a TCP client and is
subject to the port limitations. Is my thinking correct?
Thanks
Ed
----- Original Message -----
From: "Joseph Mack" <mack.joseph@xxxxxxx>
To: "LinuxVirtualServer.org users mailing list."
<lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, May 11, 2004 12:36 PM
Subject: Re: Fundamental performance limits of a linux based load balancer
/server system?
> Edward Chee wrote:
> >
> > But doesn't a load balancer act as both server and client?
>
> no it's just a router, admittedly with slightly different rules,
> but all it does it route packets
>
> Joe
> --
> Joseph Mack PhD, High Performance Computing & Scientific Visualization
> SAIC, Supporting the EPA Research Triangle Park, NC 919-541-0007
> Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
