From: Wladimir <laanwj@gmail•com>
To: Angel Leon <gubatron@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] have there been complains about network congestion? (router crashes, slow internet when running Bitcoin nodes)
Date: Tue, 8 Apr 2014 18:48:01 +0200 [thread overview]
Message-ID: <CA+s+GJBYDuoN2LeWz1dEfMhEYX+e98ORDdTTPd-=FS=4=1Lqkw@mail.gmail.com> (raw)
In-Reply-To: <CADZB0_bqzoCT7XRgaoWBZLyfoFjWvLs8-YaP9AZ=sv7x_xJbpQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]
On Tue, Apr 8, 2014 at 6:13 PM, Angel Leon <gubatron@gmail•com> wrote:
> I was wondering if the level of traffic a Bitcoin node gets is or will be
> so high that you have heard/will hear complains like the following:
>
>
> 1. a home router that crashes or slows down when its NAT pin-hole
> table overflows, triggered by many TCP connections.
>
>
The default maximum amount of connections is 125, which only happens if you
have a stable node that accepts incoming connections. The maximum number of
outgoing connections is always 8.
Should be no problem even for cheapass routers.
> 1. a home router that crashes or slows down by UDP traffic
>
> N/A - We don't use UDP
> 1. a home DSL or cable modem having its send buffer filled up by
> outgoing data, and the buffer fits seconds worth of bytes. This adds
> seconds of delay on interactive traffic. For a web site that needs 10 round
> trips to load this may mean 10s of seconds of delay to load compared to
> without bittorrent. Skype or other delay sensitive applications would be
> affected even more.
>
> Filling up the send buffer is certainly possible.
Adding throttling wouldn't be horribly hard, but this is postponed until
parallel block download is implemented, so that other peers will not get
stuck on your throttled node.
>
> 1.
>
> I was wondering if we have or expect to have these issues in the future,
> perhaps uTP could help greatly the performance of the entire network at
> some point.
>
There is enough lower-hanging fruit left.
If you're interested in speeding up the performance I think it's important
to start with benchmarking and analysis to find out where the pain points
are.
Wladimir
[-- Attachment #2: Type: text/html, Size: 3407 bytes --]
next prev parent reply other threads:[~2014-04-08 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 16:13 Angel Leon
2014-04-08 16:30 ` Matt Whitlock
2014-04-08 16:36 ` Angel Leon
2014-04-08 16:44 ` Gregory Maxwell
2014-04-08 16:48 ` Wladimir [this message]
2014-04-08 17:33 ` Angel Leon
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+GJBYDuoN2LeWz1dEfMhEYX+e98ORDdTTPd-=FS=4=1Lqkw@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gubatron@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