You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
--out-peers arg (=-1) set max number of out peers
--in-peers arg (=-1) set max number of in peers
--tos-flag arg (=-1) set TOS flag
--limit-rate-up arg (=2048) set limit-rate-up [kB/s]
--limit-rate-down arg (=8192) set limit-rate-down [kB/s]
--limit-rate arg (=-1) set limit-rate [kB/s]
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:
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: