On Wed, Mar 18, 2009 at 12:48:02PM +0000, Sihem wrote: > so if I correctly understand your reply, the closest solution to my question > is to use "balance leastconn" so that the weights of servers will be adjusted > on the fly according to the number of requests per second they have > processed. > the drawback is that this algorithm is not suited for HTTP sessions
Inside haproxy, it's possible to dynamically change the weight. This is just not exposed to the user right now. Round robin and leastconn are dynamic algorithms. The response time weight update is not yet implemented, but I'd like to add that in the short-term roadmap. I have some drafts somewhere on which I have established an algorithm to compare each server's response time to all others. So... stay tuned ;-) Willy
