mirrors/dnscrypt-proxy
1
0
Fork 0
mirror of https://github.com/DNSCrypt/dnscrypt-proxy.git synced 2025-03-04 10:24:40 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Load Balancing Options (markdown)

B00ze64 2018-04-07 01:48:00 -04:00
parent 9bcc1c3ed2
commit 94a284fd02
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Load-Balancing-Options.md

@ -35,5 +35,5 @@ The default strategy is **p2** so `DNSCrypt-Proxy` will pick one of the two fast
## 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. 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.
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 will be very fast for you.