On 21-4-2010 23:54, Willy Tarreau wrote:
>>> I want to use haproxy for content switching on a large scale (lot of >>> acls, lot of backends), but with httpclose on haproxy uses 25% cpu, >>> without httpclose haproxy uses 5% cpu. So I'd rather not use httpclose >>> if I don't have to.. >> >> Also looks ok, since if you use httpclose haproxy got more work, so >> cpu also got more work.
Trying to wrap my head around this.. I read the configuration guide, and let me see if I understand correctly: when I use the http-server-close option, connections between haproxy and the backends or not persistent, but for each request, a new connection will be established.
But this adds the overhead of connection establishment, and should increase cpu usage, not descrease it, right? What am I missing? (Keep in mind I'm only talking about the haproxy machine, don't care about the backend server.)
The http-close option does about the same thing, but it is about connection between the clients and haproxy.
To me the backend-side and the client-side are two seperate things, which have little to do with eachother. Still, you say "http-server-close is about twice as fast as httpclose". Am I not interpreting things right?
-- With kind regards, Angelo Höngens systems administrator MCSE on Windows 2003 MCSE on Windows 2000 MS Small Business Specialist ------------------------------------------ NetMatch tourism internet software solutions Ringbaan Oost 2b 5013 CA Tilburg +31 (0)13 5811088 +31 (0)13 5821239 A.Hongens#netmatch.nl www.netmatch.nl ------------------------------------------Received on 2010/04/23 13:14
This archive was generated by hypermail 2.2.0 : 2010/04/23 13:30 CEST