Willy Tarreau f09c6603d3 MEDIUM: backend: add the 'first' balancing algorithm ... The principle behind this load balancing algorithm was first imagined and modeled by Steen Larsen then iteratively refined through several work sessions until it would totally address its original goal. The purpose of this algorithm is to always use the smallest number of servers so that extra servers can be powered off during non-intensive hours. Additional tools may be used to do that work, possibly by locally monitoring the servers' activity. The first server with available connection slots receives the connection. The servers are choosen from the lowest numeric identifier to the highest (see server parameter "id"), which defaults to the server's position in the farm. Once a server reaches its maxconn value, the next server is used. It does not make sense to use this algorithm without setting maxconn. Note that it can however make sense to use minconn so that servers are not used at full load before starting new servers, and so that introduction of new servers requires a progressively increasing load (the number of servers would more or less follow the square root of the load until maxconn is reached). This algorithm ignores the server weight, and is more beneficial to long sessions such as RDP or IMAP than HTTP, though it can be useful there too.		2012-02-21 22:27:27 +01:00
..
common	MINOR: Date and time fonctions that don't use snprintf	2012-02-09 17:03:28 +01:00
import	[MAJOR] replace ultree with ebtree in wait-queues	2008-06-24 08:17:16 +02:00
proto	MEDIUM: backend: add the 'first' balancing algorithm	2012-02-21 22:27:27 +01:00
types	MEDIUM: backend: add the 'first' balancing algorithm	2012-02-21 22:27:27 +01:00