Hi all, haproxy is gr8 - simply. Till today I was using roundobin algorithm, but after studying documentation it popped up that source might be better. I'm using haproxy in tcp mode, version 1.8, load from one client sometimes requires more then few servers from the backend.
but also initialization of handling requests takes some cost - I considered picking a source as an algorithm - to avoid picking the next server according to roundrobin. But I realised that the behaviour of the queue has changed. With a source algorithm for every source(host, client) there is a separate queue and one server picked. would it be possible that when one server reaches it's slots, the next one is allocated (and next one, and next one)? where I can find detailed information on how queues are managed depending on the algorithm which is used? I understand that it is desired behaviour in http balancer but in case of tcp it is not so obvious. regards Łukasz Tasz RTKW
