On Sun, Jan 30, 2011 at 06:34:34AM -0700, Sean Hess wrote: > Ah, shoot, I forgot to mention that I'm running that ab test on ten boxes in > parallel, so actual concurrency level is 10x what ab spits out. That's why I > put "1500" above the one that had a concurrency of 150. > > Sorry for the confusion.
no problem. > I'm currently looking into keepalive stuff, going with a simpler config: > > listen main *:80 > mode http > balance roundrobin > option http-server-close > server api1 api1:80 check > server api2 api2:80 check > server api3 api3:80 check > server api4 api4:80 check > > It sounds like http-server-close makes the client -> haproxy connection stay > open, but haproxy -> app server close between requests. It doesn't really > make sense to me why that would be faster than keeping them all open all the > time, but yes, I should examine my logs and figure out where the holdup is. Right now with option httpclose, they're advertised as closed but not actively closed. The client waits for the server to close. If it does not or if it delays the close for whatever reason, it can cause what you're observing. In your logs, you'd see short request/connect/response times and a high total time. Regards, Willy
