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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gubatron@gmail.com>) id 1WXYee-0003K1-VE
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 16:13:44 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.171 as permitted sender)
client-ip=209.85.216.171; envelope-from=gubatron@gmail.com;
helo=mail-qc0-f171.google.com;
Received: from mail-qc0-f171.google.com ([209.85.216.171])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXYee-00037C-2o
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 16:13:44 +0000
Received: by mail-qc0-f171.google.com with SMTP id c9so1321628qcz.30
for <bitcoin-development@lists.sourceforge.net>;
Tue, 08 Apr 2014 09:13:38 -0700 (PDT)
X-Received: by 10.224.161.10 with SMTP id p10mr3035246qax.12.1396973618539;
Tue, 08 Apr 2014 09:13:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.90.42 with HTTP; Tue, 8 Apr 2014 09:13:18 -0700 (PDT)
From: Angel Leon <gubatron@gmail.com>
Date: Tue, 8 Apr 2014 12:13:18 -0400
Message-ID: <CADZB0_bqzoCT7XRgaoWBZLyfoFjWvLs8-YaP9AZ=sv7x_xJbpQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e01536b724b4e0d04f68a44e0
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
(gubatron[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: 1WXYee-00037C-2o
Subject: [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:13:45 -0000
--089e01536b724b4e0d04f68a44e0
Content-Type: text/plain; charset=ISO-8859-1
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.
2. a home router that crashes or slows down by UDP traffic
3. 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.
These are issues the bittorrent community faced and eventually solved
brilliantly with uTP, which uses a congestion window algorithm that allows
you to use as much of the TCP bandwidth as possible and automatically
throttling down if there's any cross traffic, while also taking into
consideration things like the optimum MTUs (Path MTU discovery), Clock
Drift phenomena and other features.
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.
Detailed information about uTP here
http://www.libtorrent.org/utp.html
@gubatron
--089e01536b724b4e0d04f68a44e0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I was wondering if the level of traffic a Bitcoin nod=
e gets is or will be so high that you have heard/will hear complains like t=
he following:<br><br><ol class=3D"" style=3D"margin:0px 0px 1em;padding:0px=
;line-height:1.8em;color:rgb(0,0,0);font-family:Verdana;font-size:13px">
<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><li style=3D"margin:0px 0px 0px 2.8em;pa=
dding:0px;font-size:12px">
a home router that crashes or slows down by UDP traffic</li><li style=3D"ma=
rgin:0px 0px 0px 2.8em;padding:0px;font-size:12px">a home DSL or cable mode=
m having its send buffer filled up by outgoing data, and the buffer fits se=
conds worth of bytes. This adds seconds of delay on interactive traffic. Fo=
r 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 sens=
itive applications would be affected even more.<br>
</li></ol><div><font color=3D"#000000" face=3D"Verdana"><span style=3D"font=
-size:12px;line-height:23.399999618530273px">These are issues the bittorren=
t community faced and eventually solved brilliantly with uTP, which uses a =
congestion window algorithm that allows you to use as much of the TCP bandw=
idth as possible and automatically throttling down if there's any cross=
traffic, while also taking into consideration things like the optimum MTUs=
(Path MTU discovery), Clock Drift phenomena and other features.=A0</span><=
br>
<br><span style=3D"font-size:12px;line-height:23.399999618530273px">I was w=
ondering if we have or expect to have these issues in the future, perhaps u=
TP could help greatly the performance of the entire network at some point.<=
/span><br>
<br><span style=3D"font-size:12px;line-height:23.399999618530273px">Detaile=
d information about uTP here</span><br><span style=3D"font-size:12px;line-h=
eight:23.399999618530273px"><a href=3D"http://www.libtorrent.org/utp.html">=
http://www.libtorrent.org/utp.html</a><br>
</span><br>@gubatron</font></div></div>
</div>
--089e01536b724b4e0d04f68a44e0--
|
