highperfocused/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2026-09-11 21:20:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: Update docs that refer to -maxconnections

Browse Source
This commit is contained in:
Martin Zumsande
2024-08-05 13:57:12 -04:00
parent 69ce0dba2a
commit c11508406e
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/reduce-memory.md
View File

@@ -33,7 +33,7 @@ The size of some in-memory caches can be reduced. As caches trade off memory usa
## Number of peers
- `-maxconnections=<n>` - the maximum number of connections, which defaults to 125. Each active connection takes up some
- `-maxconnections=<n>` - the maximum number of connections, which defaults to 200. Each active connection takes up some
memory. This option applies only if inbound connections are enabled; otherwise, the number of connections will not
be more than 11. Of the 11 outbound peers, there can be 8 full-relay connections, 2 block-relay-only ones,
and occasionally 1 short-lived feeler or extra outbound block-relay-only connection.

5
doc/reduce-traffic.md
View File

@@ -3,8 +3,9 @@ Reduce Traffic
Some node operators need to deal with bandwidth caps imposed by their ISPs.
By default, Bitcoin Core allows up to 125 connections to different peers, 11 of
which are outbound. You can therefore, have at most 114 inbound connections.
By default, Bitcoin Core allows up to 200 connections to different peers, 11 of
which are outbound. You can therefore, have at most 189 inbound connections, half of
which can only be taken up by low-traffic block-relay-only peers.
Of the 11 outbound peers, there can be 8 full-relay connections, 2
block-relay-only ones and occasionally 1 short-lived feeler or an extra block-relay-only connection.