From 6a776faff930986be8c25f28c667b2b41d86aad1 Mon Sep 17 00:00:00 2001 From: Jonas Schnelli Date: Tue, 10 Nov 2015 13:40:39 +0100 Subject: [PATCH 1/2] [doc] add documentation how to reduce traffic --- doc/reducetraffic.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 doc/reducetraffic.md diff --git a/doc/reducetraffic.md b/doc/reducetraffic.md new file mode 100644 index 000000000..085da1a28 --- /dev/null +++ b/doc/reducetraffic.md @@ -0,0 +1,36 @@ +REDUCE TRAFFIC +============== + +Some node operators need to deal with bandwith cap given by their ISPs. + +By default, bitcoin-core allows up to 125 connections to different peers, 8 of +them outbound (and therefore 117 max inbound connections). + +The default settings can result in relatively significant traffic consumption. + + +Ways to reduce traffic: + +1. Use `-maxuploadtarget=` + +A major part of the traffic is caused by serving historic blocks to other nodes +in initial blocks download state (syncing up a new node). +This option can be specified in MiB per day and is turned off by default. +This is *not* a hard limit but a threshold to minimize the outbound +traffic. When the limit is about to be reached, the uploaded data is cut by not +serving historic blocks (blocks older than one week). +Keep in mind that new nodes require other nodes that are willing to serve +historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB +per day)** + +2. Disable "listening" (`-listen=0`) + +Disable listening will result in fewer nodes connected (remind the max of 8 +outbound peers). Fewer nodes will result in less traffic usage because relaying +blocks and transaction needs to be passed to fewer nodes. + +3. Reduce maximal connections (`-maxconnections=`) + +Reducing the connected nodes to a miniumum can be desired in case traffic +limits are tiny. Keep in mind that bitcoin trustless model works best if you are +connected to a handfull of nodes. From 42bae94e344857e1f02e88628933a8b296b8a674 Mon Sep 17 00:00:00 2001 From: fanquake Date: Wed, 11 Nov 2015 18:53:48 +0800 Subject: [PATCH 2/2] [doc] Improve lanaguge in reducetraffic.md --- doc/reducetraffic.md | 35 +++++++++++++++++------------------ 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/doc/reducetraffic.md b/doc/reducetraffic.md index 085da1a28..a79571913 100644 --- a/doc/reducetraffic.md +++ b/doc/reducetraffic.md @@ -1,36 +1,35 @@ -REDUCE TRAFFIC +Reduce Traffic ============== -Some node operators need to deal with bandwith cap given by their ISPs. +Some node operators need to deal with bandwith caps imposed by their ISPs. By default, bitcoin-core allows up to 125 connections to different peers, 8 of -them outbound (and therefore 117 max inbound connections). +which are outbound. You can therefore, have at most 117 inbound connections. The default settings can result in relatively significant traffic consumption. - Ways to reduce traffic: -1. Use `-maxuploadtarget=` +## 1. Use `-maxuploadtarget=` -A major part of the traffic is caused by serving historic blocks to other nodes -in initial blocks download state (syncing up a new node). +A major component of the traffic is caused by serving historic blocks to other nodes +during the initial blocks download phase (syncing up a new node). This option can be specified in MiB per day and is turned off by default. -This is *not* a hard limit but a threshold to minimize the outbound -traffic. When the limit is about to be reached, the uploaded data is cut by not -serving historic blocks (blocks older than one week). +This is *not* a hard limit; only a threshold to minimize the outbound +traffic. When the limit is about to be reached, the uploaded data is cut by no +longer serving historic blocks (blocks older than one week). Keep in mind that new nodes require other nodes that are willing to serve historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB per day)** -2. Disable "listening" (`-listen=0`) +## 2. Disable "listening" (`-listen=0`) -Disable listening will result in fewer nodes connected (remind the max of 8 -outbound peers). Fewer nodes will result in less traffic usage because relaying -blocks and transaction needs to be passed to fewer nodes. +Disabling listening will result in fewer nodes connected (remember the maximum of 8 +outbound peers). Fewer nodes will result in less traffic usage as you are relaying +blocks and transactions to fewer nodes. -3. Reduce maximal connections (`-maxconnections=`) +## 3. Reduce maximum connections (`-maxconnections=`) -Reducing the connected nodes to a miniumum can be desired in case traffic -limits are tiny. Keep in mind that bitcoin trustless model works best if you are -connected to a handfull of nodes. +Reducing the maximum connected nodes to a miniumum could be desirable if traffic +limits are tiny. Keep in mind that bitcoin's trustless model works best if you are +connected to a handful of nodes.