Hello, On Wed, Jun 15, 2011 at 12:16:57PM +0100, Chris Allen wrote: > Hello, > > The architecture of our application is such that we are running haproxy > with a large number (perhaps 700-800) > of back-end pools, each containing a single server. Is this something > that haproxy can handle efficiently? Are > there any caveats as the number of pools increases? Perhaps memory or > CPU load?
This is something I'm used to seeing where haproxy is used as a plain simple relay to enforce timeouts or as a NAT box. There is no particular issue doing this. What you should consider however is how you will select which backend will process a request. If you're evaluating thousands of regex-based rules in order to finally decide the right backend, then it can be expensive in terms of CPU load. And even there it depends on the regex lib used and the request rate, of course. But in general it's not much an issue. Ah, another minor issue you'll notice is that the stats page is huge ;-) Regards, Willy
