mirror of
https://github.com/DNSCrypt/dnscrypt-proxy.git
synced 2025-03-04 10:24:40 +01:00
Updated Load Balancing Options (markdown)
parent
feed68a1f3
commit
4ed234c953
1 changed files with 1 additions and 1 deletions
|
@ -35,5 +35,5 @@ The default strategy is **p2** so `DNSCrypt-Proxy` will pick one of the two fast
|
||||||
|
|
||||||
## Some Remarks
|
## Some Remarks
|
||||||
|
|
||||||
If you enable logging and have a look at the `DNSCrypt-Proxy` log, you will see the response times of all your servers when the proxy starts. Since there are so few DNSCrypt servers out there, you should notice that only a few servers are very fast for you, with the majority being appreciably slower. What this means is that if you have a relatively large list of random server from around the world, and you chose the **ph** strategy, some of your queries will probably end-up using slower servers; **p2** is probably the best strategy to use. However, **ph** would probably be pretty good if you were choosing regular DNS servers, since there are thousands and many would be very fast for you.
|
If you enable logging and have a look at the `DNSCrypt-Proxy` log, you will see the response times of all your servers when the proxy starts. Since there are so few DNSCrypt servers out there, you should notice that only a few servers are very fast for you, with the majority being appreciably slower. What this means is that if you have a relatively large list of random server from around the world, and you chose the **ph** strategy, some of your queries will probably end-up using slower servers; **p2** is probably the best strategy to use. However, **ph** would be pretty good if you were choosing regular DNS servers, since there are thousands of those and many would be very fast for you (you can easily find 50 fast servers for any location in North-America).
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue