-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default monerod configuration speedup #9275
Comments
Increasing the number of out peers has an impact on privacy and network topology. We won't do any changes to it without corresponding research. The bandwidth limits could be increased but as far as I know even during the recent spam attack the limit wasn't reached.
This makes it easier to sybil attack the network. |
Why are the default monerod configurations very low?
Download is limited to 8 MiB/s, upload is limited to 2 MiB/s, and the maximum number of peers to download from (in) is limited to 12.
Could we increase the default limits to 1024 MiB/s download, 1024 MiB/s upload, 512 in_peers, and 512 out_peers?
Torrenting software typically don't have artificial transfer speed limits and they manage fine. We should too.
./monerod --help shows
These limits are all what is by default, except the
--out-peers arg (=-1)
, which is actually 12. Maybe this was changed, or perhaps 12 is a fallback value from an incorrect configuration. If you pass-1
as any of the arguments, it doesn't set it to unlimited but retains the default (which may be a fallback).Maybe you would also want to increase the default maximum number of connections per ip from 1 to 32 or remove the restriction completely, as this impacts users with shared ips (same network, large business, VPN, cloud provider) when there are a large number of monero users on the same network.
The text was updated successfully, but these errors were encountered: