mirror of
https://github.com/DNSCrypt/dnscrypt-proxy.git
synced 2025-03-04 02:14:40 +01:00
Updated Load Balancing Options (markdown)
parent
83d2d9ef18
commit
9bcc1c3ed2
1 changed files with 3 additions and 1 deletions
|
@ -22,13 +22,15 @@ Over time, every server that is queried is compared with all the other servers a
|
|||
|
||||
## Your Load Balancing Options
|
||||
|
||||
So the servers are sorted from quickest to slowest. The load balancing is done using that list. You have a choice of 4 different ranges/sets from which to chose the server that will next be queried. The server is chosen randomly inside that set. The 4 possible values of the `lb_strategy =` parameter are:
|
||||
So the servers are sorted from quickest to slowest. The load balancing is done using that list. You have a choice of 4 different ranges/sets from which to chose the server that will next be queried. The server is chosen randomly inside that set. The 4 possible values of the `lb_strategy` parameter are:
|
||||
|
||||
* **fastest** (always pick the one fastest server in the list)
|
||||
* **p2** (randomly chose between the top 2 fastest servers)
|
||||
* **ph** (randomly chose between the top fastest half of all servers)
|
||||
* **random** (just pick any random server from the list)
|
||||
|
||||
This setting is a string, so you use `lb_strategy = 'p2'` in the configuration file.
|
||||
|
||||
The default strategy is **p2** so `DNSCrypt-Proxy` will pick one of the two fastest servers. It will compare how fast that server was with a randomly chosen server and if that random server is faster, the random server will move up. The same is true for all strategies - random servers will move up in the list when they are faster than the server that was just queried.
|
||||
|
||||
## Some Remarks
|
||||
|
|
Loading…
Add table
Reference in a new issue