doc: add maxuploadtarget to bitcoinf.conf example #21499

apitko commented at 5:47 AM on March 22, 2021: contributor

I reduced mine to 10000 since I was seeing about 40GB+ a day being uploaded and need to utilize my bandwidth for other projects. Running bitcoin-qt on a Raspberry Pi 4 with a gig fiber connection. Would be interested if maxconnections is a better use to throttle than upload limits or if this suggested parameter can cause issues. So far throttling looks much better for me. Thank you for the conf file!

fanquake commented at 5:53 AM on March 22, 2021: member

Note the CI is failing due to:

⚠️ User is too new to use Community clusters! Please check with support! @fkorotkov what is the threshold for new GitHub accounts before the CI will run?

ghost commented at 6:09 AM on March 22, 2021: none

Is this related to reddit post: https://www.reddit.com/r/Bitcoin/comments/m88pad/full_nodes_and_isp_data_caps/ ?

Running bitcoin-qt on a Raspberry Pi 4 with a gig fiber connection.

Umbrel?

Would be interested if maxconnections is a better use to throttle than upload limits or if this suggested parameter can cause issues.

Two solutions suggested in the above reddit link:

I've heard people reporting that they uploaded several TB in a few days when they have peerblockfilters by Greg Maxwell

https://github.com/getumbrel/umbrel/blob/master/templates/bitcoin-sample.conf#L28

maxuploadtarget can also be used to manage upload limits

fkorotkov commented at 2:27 PM on March 22, 2021: none

@fanquake it's 12 hours since user creation.

We've been battling with people creating fake accounts and using CIs available on GitHub including Cirrus for mining different crypto coins. 😪 This is just the first dump mechanism that prevents the bad actors to just re-create a new user right away.

Is it OK to wait for an hour so @apitko or you can re-run all the tasks on this page.

ghost commented at 5:08 PM on March 22, 2021: none

According to bitcoind --help version 0.21.0 maxuploadtarget is in MiB, so you should change MB to MiB and GB to GiB.

apitko commented at 5:17 PM on March 22, 2021: contributor

According to bitcoind --help version 0.21.0 maxuploadtarget is in MiB, so you should change MB to MiB and GB to GiB.

Good catch! Will update to Mebi and Gibi.

MarcoFalke added the label Waiting for author on Mar 22, 2021

apitko commented at 2:05 AM on March 23, 2021: contributor

Bee a while since I used Github! How can I edit a commit? i was only trying to submit a suggestion, was a bit tired Wanted to change MB to MiB and GB to GiB for clarity.

fanquake renamed this:
~~Update bitcoin.conf~~
doc: add maxuploadtarget to bitcoinf.conf example
on Mar 23, 2021

fanquake commented at 2:37 AM on March 23, 2021: member

@fkorotkov thanks for clarifying. @apitko Take a look at https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#contributor-workflow.

michaelfolkson commented at 11:25 AM on March 23, 2021: contributor

@apitko: Make the additional change on your PR branch, commit that change, squash the two commits and then force git push (git push -f).

jarolrod commented at 8:52 PM on April 12, 2021: member

@apitko any update? Are you going to get back to this?

apitko commented at 11:12 PM on April 12, 2021: contributor

@jarolrod Had total hip replacement surgery and computer work went by the wayside. Jumping on this to button up tomorrow. Thanks!

fanquake commented at 12:13 AM on April 13, 2021: member

@apitko you'll need to squash your commits. You can use doc: add maxuploadtarget to bitcoinf.conf example as the commit message.

doc: add maxuploadtarget to bitcoinf.conf example

Update bitcoin.conf

I reduced mine to 10000 since I was seeing about 40GB+ a day being uploaded and need to utilize my bandwidth for other projects. I run a gig fiber connect. Would be interested if maxconnections is a better use to throttle than upload limits or if this suggested parameter causes issues. Thanks for the file example!

Update bitcoin.conf

e21b92be84

apitko force-pushed on Apr 13, 2021

apitko commented at 12:50 AM on April 13, 2021: contributor

@fanquake Thank you! Been awhile, a bit rusty with git.

fanquake removed the label Waiting for author on Apr 13, 2021

fanquake added the label Docs on Apr 13, 2021

doc: add maxuploadtarget to bitcoinf.conf - changed 1GiB to 1 GiB

test: remove duplicate assertions in util_tests

Co-authored-by: Kiminuo <kiminuo@protonmail.com>

doc: add maxuploadtarget to bitcoinf.conf example

Update bitcoin.conf

I reduced mine to 10000 since I was seeing about 40GB+ a day being uploaded and need to utilize my bandwidth for other projects. I run a gig fiber connect. Would be interested if maxconnections is a better use to throttle than upload limits or if this suggested parameter causes issues. Thanks for the file example!

Update bitcoin.conf

3abdc6b9ef

Merge branch 'patch-1' of https://github.com/apitko/bitcoin into patch-1 c7a5e14590

Update bitcoin.conf 2ccf26bc79

in share/examples/bitcoin.conf:69 in e21b92be84 outdated

  65 | @@ -66,6 +66,10 @@
  66 |  # Maximum number of inbound+outbound connections.
  67 |  #maxconnections=
  68 |  
  69 | +#Maximum daily upload target in MiB per day (e.g. 'maxuploadtarget=1024' is 1GiB max throughput per day)

unknown commented at 4:51 AM on April 13, 2021:

I'd like 1 GiB better.

apitko commented at 6:17 AM on April 13, 2021:

@wodry I like it better too. Let's see if I got my squashing and commit correct.

theStack commented at 2:26 PM on April 18, 2021: member

Concept ACK - happy to review as soon as the commits are squashed into one :)

in share/examples/bitcoin.conf:71 in 2ccf26bc79

  65 | @@ -66,6 +66,10 @@
  66 |  # Maximum number of inbound+outbound connections.
  67 |  #maxconnections=
  68 |  
  69 | +#Maximum daily upload target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB max throughput per day)
  70 | +#Limiting the free-for-all bandwidth uploads for those with bandwidth limits
  71 | +#maxuploadtarget=

jonatack commented at 2:53 PM on April 18, 2021:

suggestion

-#Maximum daily upload target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB max throughput per day)
-#Limiting the free-for-all bandwidth uploads for those with bandwidth limits
+# Maximum upload bandwidth target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB per day).
+# This limits the upload bandwidth for those with bandwidth limits. 0 = no limit (default: 0).

"daily upload target in MiB per day" is redundant (daily/per day)
mention the default and that 0 = no limit
missing space between # and the comments

jonatack commented at 2:55 PM on April 18, 2021:

maybe mention that it does not apply to peers with "download" permission

$ bitcoind -help | grep -A3 maxuploadtarget=
  -maxuploadtarget=<n>
       Tries to keep outbound traffic under the given target (in MiB per 24h).
       Limit does not apply to peers with 'download' permission. 0 = no
       limit (default: 0)

apitko commented at 7:31 PM on April 26, 2021:

Awesome! Will get to this shortly. I am having trouble squashing after I enabled 2FA and CLI won't allow me to authorize now to squash. I am also trying the Desktop version and does not give me a squash option, tried researching, any help appreciated.

luke-jr commented at 10:45 PM on May 13, 2021: member

Maybe also reference doc/reduce-traffic.md in the comments?

jarolrod commented at 2:41 AM on May 27, 2021: member

pinging @apitko. If you can't or don't want to revisit this, you can close this PR and I will pick it up and squash.

apitko commented at 2:51 AM on May 27, 2021: contributor

@jarolrod Thank you Jarol! I've tried everything to squash the my commits using web, CLI and app based Git and it won't allow me with 2FA. Please feel free to pickup and squash. Frustration got the best of me. And @jonatack had a good mention to add. Quoting @jonatack mention here:

$ bitcoind -help | grep -A3 maxuploadtarget= -maxuploadtarget=<n> Tries to keep outbound traffic under the given target (in MiB per 24h). Limit does not apply to peers with 'download' permission. 0 = no limit (default: 0)

jarolrod commented at 3:33 AM on May 27, 2021: member

@aptiko no problem! done in #22080

apitko commented at 4:17 AM on May 27, 2021: contributor

@jarolrod You are awesome! Will close. Cheers!

apitko closed this on May 27, 2021

MarcoFalke referenced this in commit 8462cd5601 on May 31, 2021

sidhujag referenced this in commit 6d84a579a6 on Jun 1, 2021

PastaPastaPasta referenced this in commit ceaaf1955b on Jun 27, 2021

PastaPastaPasta referenced this in commit a154c84ffe on Jun 28, 2021

PastaPastaPasta referenced this in commit 134cb9c269 on Jun 29, 2021

PastaPastaPasta referenced this in commit b3f7a98db7 on Jul 1, 2021

PastaPastaPasta referenced this in commit b5dbbc2418 on Jul 1, 2021

PastaPastaPasta referenced this in commit 509d69a641 on Jul 15, 2021

PastaPastaPasta referenced this in commit d2bf2dd4a1 on Jul 15, 2021

PastaPastaPasta referenced this in commit 8bf157ee80 on Jul 16, 2021

gabriel-bjg referenced this in commit 29cc67e117 on Jul 16, 2021

DrahtBot locked this on Aug 16, 2022