BeginToLearn
asked on
least response method
hi all,
I am reading about least response method in network load balancer. Could you please tell me some pro and con of this technique? tks a lot.
I am reading about least response method in network load balancer. Could you please tell me some pro and con of this technique? tks a lot.
ASKER
i did. however, i can't find the advantages and disadvantages of this technique
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i am doing research on each technique of LB and find out disadvantage/advantage of each technique. i get stuck with least response technique.
those different LB techniques can be judged as "Recommended For" becuase advantages and disadvatages related also to the applications, budget, infrastructure, usage or load, OS .. etc.
to clearify that there is no disadvantage with Round Roben ( Other than directing to stalled servers) for static web sites running on servers with the same configuration, but the disadvantage list will grow when you have asp.net
to clearify that there is no disadvantage with Round Roben ( Other than directing to stalled servers) for static web sites running on servers with the same configuration, but the disadvantage list will grow when you have asp.net
ASKER
here is what i wrote about round robin disadvantages:
Disadvantages: It is difficult to manage the client cache and reusability. Clients will cache the IP addresses that have been used successfully in request in order to increase performance. Same IP address record can be returned to multiple clients. Consequently, the purpose of load balancing is eliminated. In addition, Round Robin DNS doesn’t deal with the available services in server-side. If a server is off or down, its hosting IP addresses are still retuned. Using Round Robin DNS also can’t map a client to a same specific server because the alternative IP address is issued to each request
Disadvantages: It is difficult to manage the client cache and reusability. Clients will cache the IP addresses that have been used successfully in request in order to increase performance. Same IP address record can be returned to multiple clients. Consequently, the purpose of load balancing is eliminated. In addition, Round Robin DNS doesn’t deal with the available services in server-side. If a server is off or down, its hosting IP addresses are still retuned. Using Round Robin DNS also can’t map a client to a same specific server because the alternative IP address is issued to each request
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
how about advantages of this technique?
Advantage would be that in theory, the server with the least connections and best response time will get the traffic assigned to it.
FYI, I always use persistence, either cookie or source IP.
FYI, I always use persistence, either cookie or source IP.
ASKER
I am thinking of 1 more advantage and 1 more disadvantage. If you know, please let me know.
Is this a test?
ASKER
nope. This is the research paper about all LB techniques
If you can think of 1 more advantage and disadvantage, by all means, write them down.
ASKER
I think this maybe the advantage: high performance server will take more work load
True, I agree with that.
ASKER
are you good at c/C++ program?
Not anymore, no.
ASKER
tks for your help. let me close this question.
http://community.citrix.co