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
|
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 1WXZ0l-0004cd-0y
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 16:36:35 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.178 as permitted sender)
client-ip=209.85.216.178; envelope-from=gubatron@gmail.com;
helo=mail-qc0-f178.google.com;
Received: from mail-qc0-f178.google.com ([209.85.216.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXZ0j-0003zp-63
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 16:36:34 +0000
Received: by mail-qc0-f178.google.com with SMTP id i8so1378961qcq.9
for <bitcoin-development@lists.sourceforge.net>;
Tue, 08 Apr 2014 09:36:27 -0700 (PDT)
X-Received: by 10.224.161.10 with SMTP id p10mr3220558qax.12.1396974987671;
Tue, 08 Apr 2014 09:36:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.90.42 with HTTP; Tue, 8 Apr 2014 09:36:07 -0700 (PDT)
In-Reply-To: <3054815.493DgUE4ho@crushinator>
References: <CADZB0_bqzoCT7XRgaoWBZLyfoFjWvLs8-YaP9AZ=sv7x_xJbpQ@mail.gmail.com>
<3054815.493DgUE4ho@crushinator>
From: Angel Leon <gubatron@gmail.com>
Date: Tue, 8 Apr 2014 12:36:07 -0400
Message-ID: <CADZB0_Zcx7qOsb0ViTFCGs7ve5oBqx6VB0vQfEnA8cxC8LSVmA@mail.gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=089e01536b72e67e1704f68a956e
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: 1WXZ0j-0003zp-63
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:36:35 -0000
--089e01536b72e67e1704f68a956e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
only that in the real world most routers suck and people don't even know
how to configure them (reminds me of the convo about people not installing
plugins)
this is why the wheel had to be reinvented for the bittorrent world, and it
works.
http://twitter.com/gubatron
On Tue, Apr 8, 2014 at 12:30 PM, Matt Whitlock <bip@mattwhitlock.name>wrote=
:
> On Tuesday, 8 April 2014, at 12:13 pm, Angel Leon wrote:
> > 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.
>
> Or people could simply learn to configure their routers correctly. The
> only time I ever notice that Bitcoind is saturating my upstream link is
> when I try to transfer a file using SCP from a computer on my home networ=
k
> to a computer out on the Internet somewhere. SCP sets the "maximize
> throughput" flag in the IP "type of service" field, and my router
> interprets that as meaning low priority, and so those SCP transfers get
> stalled behind Bitcoind. But mostly everything else (e.g., email, web
> browsing, instant messaging, SSH) shows no degration whatsoever regardles=
s
> of what Bitcoind is doing. The key is to move the packet queue from the
> cable modem into the router, where intelligent decisions about packet
> priority and reordering can be enacted.
>
> =B5TP pretty much reinvents the wheel, and it does so in userspace, where
> the overhead is greater. There's no need for it if proper QoS is in effec=
t.
>
--089e01536b72e67e1704f68a956e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">only that in the real world most routers suck and people d=
on't even know how to configure them (reminds me of the convo about peo=
ple not installing plugins)<div>this is why the wheel had to be reinvented =
for the bittorrent world, and it works.</div>
</div><div class=3D"gmail_extra"><br clear=3D"all"><div><a href=3D"http://t=
witter.com/gubatron" target=3D"_blank">http://twitter.com/gubatron</a><br><=
/div>
<br><br><div class=3D"gmail_quote">On Tue, Apr 8, 2014 at 12:30 PM, Matt Wh=
itlock <span dir=3D"ltr"><<a href=3D"mailto:bip@mattwhitlock.name" targe=
t=3D"_blank">bip@mattwhitlock.name</a>></span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
<div class=3D"">On Tuesday, 8 April 2014, at 12:13 pm, Angel Leon wrote:<br=
>
> I was wondering if we have or expect to have these issues in the futur=
e,<br>
> perhaps uTP could help greatly the performance of the entire network a=
t<br>
> some point.<br>
<br>
</div>Or people could simply learn to configure their routers correctly. Th=
e only time I ever notice that Bitcoind is saturating my upstream link is w=
hen I try to transfer a file using SCP from a computer on my home network t=
o a computer out on the Internet somewhere. SCP sets the "maximize thr=
oughput" flag in the IP "type of service" field, and my rout=
er interprets that as meaning low priority, and so those SCP transfers get =
stalled behind Bitcoind. But mostly everything else (e.g., email, web brows=
ing, instant messaging, SSH) shows no degration whatsoever regardless of wh=
at Bitcoind is doing. The key is to move the packet queue from the cable mo=
dem into the router, where intelligent decisions about packet priority and =
reordering can be enacted.<br>
<br>
=B5TP pretty much reinvents the wheel, and it does so in userspace, where t=
he overhead is greater. There's no need for it if proper QoS is in effe=
ct.<br>
</blockquote></div><br></div>
--089e01536b72e67e1704f68a956e--
|
