summaryrefslogtreecommitdiff
path: root/de/2f9aaf451ab4bd46d0df9a95f7cab5250e3ebc
blob: a0a065b689c2636e473e601472291f8b9020b530 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WXZBv-0001jV-Fc
	for bitcoin-development@lists.sourceforge.net;
	Tue, 08 Apr 2014 16:48:07 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.52 as permitted sender)
	client-ip=209.85.219.52; envelope-from=laanwj@gmail.com;
	helo=mail-oa0-f52.google.com; 
Received: from mail-oa0-f52.google.com ([209.85.219.52])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WXZBu-0004U1-Ku
	for bitcoin-development@lists.sourceforge.net;
	Tue, 08 Apr 2014 16:48:07 +0000
Received: by mail-oa0-f52.google.com with SMTP id l6so1342270oag.11
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 08 Apr 2014 09:48:01 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.50.163 with SMTP id d3mr4056200oeo.51.1396975681292; Tue,
	08 Apr 2014 09:48:01 -0700 (PDT)
Received: by 10.182.120.66 with HTTP; Tue, 8 Apr 2014 09:48:01 -0700 (PDT)
In-Reply-To: <CADZB0_bqzoCT7XRgaoWBZLyfoFjWvLs8-YaP9AZ=sv7x_xJbpQ@mail.gmail.com>
References: <CADZB0_bqzoCT7XRgaoWBZLyfoFjWvLs8-YaP9AZ=sv7x_xJbpQ@mail.gmail.com>
Date: Tue, 8 Apr 2014 18:48:01 +0200
Message-ID: <CA+s+GJBYDuoN2LeWz1dEfMhEYX+e98ORDdTTPd-=FS=4=1Lqkw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Angel Leon <gubatron@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c309da3e50fc04f68abf00
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WXZBu-0004U1-Ku
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)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 16:48:07 -0000

--001a11c309da3e50fc04f68abf00
Content-Type: text/plain; charset=UTF-8

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

--001a11c309da3e50fc04f68abf00
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Tue, Apr 8, 2014 at 6:13 PM, Angel Leon <span dir=3D"ltr">&lt;<a href=3D=
"mailto:gubatron@gmail.com" target=3D"_blank">gubatron@gmail.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I was wondering if the=
 level of traffic a Bitcoin node gets is or will be so high that you have h=
eard/will hear complains like the following:<br>
<br><ol style=3D"line-height:1.8em;font-size:13px;font-family:Verdana;margi=
n:0px 0px 1em;padding:0px">

<li style=3D"margin:0px 0px 0px 2.8em;padding:0px;font-size:12px">a home ro=
uter that crashes or slows down when its NAT pin-hole table overflows, trig=
gered by many TCP connections.</li></ol></div></div></blockquote><div><br>
</div><div>The default maximum amount of connections is 125, which only hap=
pens if you have a stable node that accepts incoming connections. The maxim=
um number of outgoing connections is always 8.<br></div><div>Should be no p=
roblem even for cheapass routers.<br>
</div><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><ol style=3D=
"line-height:1.8em;font-size:13px;font-family:Verdana;margin:0px 0px 1em;pa=
dding:0px">
<li style=3D"margin:0px 0px 0px 2.8em;padding:0px;font-size:12px">

a home router that crashes or slows down by UDP traffic</li></ol></div></di=
v></blockquote><div>N/A - We don&#39;t use UDP<br> <br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<div dir=3D"ltr"><div><ol style=3D"line-height:1.8em;font-size:13px;font-fa=
mily:Verdana;margin:0px 0px 1em;padding:0px"><li style=3D"margin:0px 0px 0p=
x 2.8em;padding:0px;font-size:12px">a home DSL or cable modem having its se=
nd 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 th=
at needs 10 round trips to load this may mean 10s of seconds of delay to lo=
ad compared to without bittorrent. Skype or other delay sensitive applicati=
ons would be affected even more.<br>
</li></ol></div></div></blockquote><div>Filling up the send buffer is certa=
inly possible.<br></div><div>Adding throttling wouldn&#39;t be horribly har=
d, but this is postponed until parallel block download is implemented, so t=
hat other peers will not get stuck on your throttled node.<br>
</div><div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><ol s=
tyle=3D"line-height:1.8em;font-size:13px;font-family:Verdana;margin:0px 0px=
 1em;padding:0px">
<li style=3D"margin:0px 0px 0px 2.8em;padding:0px;font-size:12px">

</li></ol><div><font color=3D"#000000" face=3D"Verdana"><span style=3D"font=
-size:12px;line-height:23.399999618530273px">I was wondering if we have or =
expect to have these issues in the future, perhaps uTP could help greatly t=
he performance of the entire network at some point.</span><br>
</font></div></div></div></blockquote><div><br></div><div>There is enough l=
ower-hanging fruit left.<br><br></div><div>If you&#39;re interested in spee=
ding up the performance I think it&#39;s important to start with benchmarki=
ng and analysis to find out where the pain points are.<br>
</div>=C2=A0<br><div>Wladimir<br><br></div></div></div></div>

--001a11c309da3e50fc04f68abf00--