diff options
author | Simon Rettberg | 2016-03-23 13:56:28 +0100 |
---|---|---|
committer | Simon Rettberg | 2016-03-23 13:56:28 +0100 |
commit | 012dfedd998d9c7d17e76237ff38c5ff721d66c3 (patch) | |
tree | 676d845de7cc6d82f78a0a5da0d87b64fd09935e /conf | |
parent | [SERVER] Fix formatting (diff) | |
download | dnbd3-012dfedd998d9c7d17e76237ff38c5ff721d66c3.tar.gz dnbd3-012dfedd998d9c7d17e76237ff38c5ff721d66c3.tar.xz dnbd3-012dfedd998d9c7d17e76237ff38c5ff721d66c3.zip |
[FUSE] Add new load balancing mechanism
The new mechanism is supposed to complement the existing
RTT based balancing. While the RTT-averaging approach is
better suited to react to sudden drastic changes in server
latency.
The new approach doesn't directly consider RTT, but keeps
track of how many consecutive times each server was the best
server when measuring the RTTs. The higher that counter
rises, the more likely it will become that the connection
switches over to that server.
Eg.: Server 1 measures 600µs each time
Server 2 measures 599µs each time
After a while, in case server 1 is currently used, the
connection will eventually switch over to server 2. The
RTT-based mechanism would not switch over in this case,
since the threshold that prevents constant switching between
servers is not reached.
The new approach is meant to handle scenarios where the
network is generally fast, but it would still be beneficial
from a network topology point of view if the clients switch
to the slightly faster server, assuming it is closer to the
client and thus less network segments are burdened.
Diffstat (limited to 'conf')
0 files changed, 0 insertions, 0 deletions