My recommendation is that you do none of the things that you are looking at for optimal performance. Instead, opt for a seperate hardware solution. We went through this about a year ago when we were architecting a solution for my employers site. Admittedly, takes more traffic than you do, but we found that the dedicated hardware device offers many advantages (including layer 7 routing capablity) which we have found to be extremely useful and well worth the extra cabbage.
Cisco (and several other folks as well) make some fine load balancing hardware devices. Alteon makes one, I know . We evaluated it, but we got a better price and better support from Cisco so we went with the CSS even though I was as impressed with their device. I'm sure that there are lower end alternative, but it depends on what kind of load balancing you want to do. Do you want to do "round robin"? If not, then what criteria do you want to use? ----- Original Message ----- From: "Steven Lembark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 14, 2001 3:15 AM Subject: Re: load balancing on apache > > > -- Hemant Singh <[EMAIL PROTECTED]> > > > Hi All > > > > I am planning to host an application and its size is going to be big one > > , so expect the concurrent number of connection s to be around 2200.To > > combat the same , want to perform load sharing on 3-4 servers.So the ide > > is to put one machine on external IP and this machine , after receiving > > the requests would forward them to any of the other three machines having > > the application deployed and running on the same environment.Pls suggest > > how can i achieve this on apache. > > Randal Schwartz had a good article on this about a year > ago. You can use the re-write phase to balance the load > w/in Apache if you want to. Alternatives include round- > robin DNS and separate load balancing software. > > -- > Steven Lembark 2930 W. Palmer > Workhorse Computing Chicago, IL 60647 > +1 800 762 1582
