NimbostratusHow can we decide which method of load balancing (Round Robin, Least Connection or etc) is appropriate for particular applications?
This depends on application architecture and hardware requirements. let say you have hardware with same specifications then Least Connection method is recommended. If there is any difference between specs then you can use Ration based on members/nodes.
CirrusThis depends on application architecture and hardware requirements. let say you have hardware with same specifications then Least Connection method is recommended. If there is any difference between specs then you can use Ration based on members/nodes.
NimbostratusThanks, Emad
Yes, it's true, all this depend on the requirements. But for knowledge purpose, i have some doubts for selecting these methods.
round robin :- best for ? Least connection :- best for ? fastest response :- best for ?
etc................
regards, Jaspreet
Cirrostratusround robin :- Same hardware & Same Response time from application/DB for all requests
Least connection :- Same hardware & different Response time from application/DB for requests. Like one requests take 1 sec to process and other type of request takes 200ms then least connection will be used. Same goes for fastest response I think but never used this one.
CirrostratusThis link will help to understand load balancing methods. Go to "Local Traffic Manager load balancing methods" and check when to use column.
MVPHi Gurmjaspreet,
the "Least Connection" load balancing algorythm is considered as the best choice in 99 out of 100 usecases.
In some cases (very low traffic with OneConnect enabled) you may get better results by using a Round Robin balancing method. And in some other cases you may want to use a load balancing algorythm based on the actual load of your pool members (aka. dynamic load balancing via %CPU, amount of allocated RAM, etc.).
Cheers, Kai