From: "Bjørn Øivind Bjørnsen" <bo.bjornsen@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
Date: Mon, 19 May 2014 14:24:35 +0200 [thread overview]
Message-ID: <5379F803.40509@gmail.com> (raw)
In-Reply-To: <CANEZrP28PQNwuLYTgzyaTDUY-Sg2fEijiPZ26k3NbwvgYoqLww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On 19/05/14 14:15, Mike Hearn wrote:
> As an interested party not intimately familiar with the bitcoin codebase
> who also spent some time setting up a node a while ago, I would like to
> add one thing to the above list - network rate limiting.
>
>
> The problem is that this is easier said than done. Bitcoin Core won't
> notice a remote peer is working but slow and switch to a faster one, and
> even if it did, it'd just mean throttling your connection would cause
> all remote nodes to give up and hit the other unthrottled peers even more.
>
Does this mean that you can currently actively hurt the network by
adding a node with a very slow upstream / downstream? If so, what is the
recommended minimum amount of bandwidth you should allocate for a node?
I've already throttled mine with QoS based on the script in the contrib/
folder.
Bjørn Øivind
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-05-19 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 17:43 [Bitcoin-development] About the small number of bitcoin nodes Raúl Martínez
2014-05-18 20:15 ` Raúl Martínez
2014-05-19 7:11 ` Jeff Garzik
2014-05-19 7:25 ` Justus Ranvier
2014-05-19 14:02 ` Scott Howard
2014-05-19 8:48 ` Wladimir
2014-05-19 10:39 ` Wladimir
2014-05-19 10:47 ` Felipe Micaroni Lalli
2014-05-19 9:26 ` Bjørn Øivind Bjørnsen
2014-05-19 12:15 ` Mike Hearn
2014-05-19 12:24 ` Bjørn Øivind Bjørnsen [this message]
2014-05-19 12:28 ` Mike Hearn
2014-05-19 12:44 ` Wladimir
2014-05-19 12:53 ` Mike Hearn
2014-06-30 10:16 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5379F803.40509@gmail.com \
--to=bo.bjornsen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox