From: Wladimir <laanwj@gmail•com>
To: "Bjørn Øivind Bjørnsen" <bo.bjornsen@gmail•com>
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:44:24 +0200 [thread overview]
Message-ID: <CA+s+GJCzks9RRi8HgFbPJ+zmuona26QCpYX8Eax+Qg6WmDd2fQ@mail.gmail.com> (raw)
In-Reply-To: <5379CE4D.5040100@gmail.com>
On Mon, May 19, 2014 at 11:26 AM, Bjørn Øivind Bjørnsen
<bo.bjornsen@gmail•com> wrote:
> On 18/05/14 19:43, Raúl Martínez wrote:
>> <snip some good ideas>
>
> 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.
There is already an (old) patch that implements that. It won't be
merged, though, until headers-first and parallel block download is in.
Only when the node can download blocks from multiple peers at once it
is really safe to allow limiting rates.
(sure - there are tricks to limit rates anyway, like the script in
contrib/qos, but to have it generally available the block download
needs to be more robust first)
Wladimir
next prev parent reply other threads:[~2014-05-19 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 17:43 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
2014-05-19 12:28 ` Mike Hearn
2014-05-19 12:44 ` Wladimir [this message]
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=CA+s+GJCzks9RRi8HgFbPJ+zmuona26QCpYX8Eax+Qg6WmDd2fQ@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bo.bjornsen@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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