summaryrefslogtreecommitdiff
path: root/47/2cbf1095ee03e3ca50f00084980ee6c56e2d12
blob: 49e0c3b69acbbd72fc7969b0d59d4589ed058dfd (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
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
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 <yifu@coinapex.com>) id 1YzSvT-0008O2-EH
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 16:50:59 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of coinapex.com
	designates 209.85.223.197 as permitted sender)
	client-ip=209.85.223.197; envelope-from=yifu@coinapex.com;
	helo=mail-ie0-f197.google.com; 
Received: from mail-ie0-f197.google.com ([209.85.223.197])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YzSvR-0001F5-IS
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 16:50:59 +0000
Received: by ieua9 with SMTP id a9so35447868ieu.0
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 01 Jun 2015 09:50:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=C1gCJrEzWno1iuYU9orC7K+BeYrwhhcr/1qgAhoGjTc=;
	b=Mx7/MYr9lmejUU8GQl/Y6fI3W5mnGMaeIn01BUuIu5JOOGoOHFnvxZxN06pqxNlxKi
	2pyQFb4kqIBG2Qjyc/uTfzyw1CH0fQk+8mSABH5wMevlrB/Wwcw7F6LkmfVAuMumBlO3
	vYqboh9zUHYAaGCXVRL1CmgFmjCm2JwnSo3PKxoTRlygYknfR//nPcjPGv8206nP4WYS
	t7+Vo9/5AzrOR28yrpE1OPJNWjdg4N7/nQaNZ4bl7vf8KQgPAFXNjz3lZQS6RfMP/+D1
	LGJreaxL/v1p6/MZznsxy0mgRR5MXmmXW0TsGxCwo+AAziwkmv++gh627sbGlrZntfWJ
	sHiQ==
X-Gm-Message-State: ALoCoQkhMWSdQHWrnU5Yu6sSS8tUkddqP+A94oFw9BK4EltuzMHZ06kjKQgklt0QWGgTD3uc9oZm
MIME-Version: 1.0
X-Received: by 10.202.107.77 with SMTP id g74mr17957421oic.120.1433177018607; 
	Mon, 01 Jun 2015 09:43:38 -0700 (PDT)
Received: by 10.202.115.83 with HTTP; Mon, 1 Jun 2015 09:43:38 -0700 (PDT)
In-Reply-To: <CABsx9T2aEvPs68pQA-KrtaDQFcTTtiB36eqKAcJRkiOFQr6WsA@mail.gmail.com>
References: <554BE0E1.5030001@bluematt.me>
	<CAFzgq-xByQ1E_33_m3UpXQFUkGc78HKnA=7XXMshANDuTkNsvA@mail.gmail.com>
	<CABsx9T0kbRe31LMwk499MQUw225f5GGd67GfhXBezHmDqxkioA@mail.gmail.com>
	<CAFzgq-z5WCznGhbOexS0XESNGAVauw45ewEV-1eMij7yDT61=Q@mail.gmail.com>
	<CAFzgq-zTybEQyGz0nq90u5n5JZcJzxQS_XKaTpr5POJi-tHM6A@mail.gmail.com>
	<CABsx9T2L5bi-c63-KqSifOMeNayUWSPo0_Hx8VjMR_4=kC3ixg@mail.gmail.com>
	<CAE28kUT61qYxqV0mOqw5Dan=eMiCvnG2SnsAeWzOWTxwLydyeQ@mail.gmail.com>
	<CABsx9T2hfpts5y_M6PdDcxmq9Q2smesJ0Nmp9a9iyPD_MoPC9g@mail.gmail.com>
	<CAE28kUTZV3YsaSCX2d5YwLetnf=f+bOWGrwxLXdZFywTZ=+Pjg@mail.gmail.com>
	<CALC81CNq-GK5q6R4bmgHL5_Ej2+cZrtQMMLVmuhvMxkZokM3hQ@mail.gmail.com>
	<CAE28kUQr+kUPak67tcNQGGscUXtJiD1LiXfjdD8_LMUWyVdR5w@mail.gmail.com>
	<CANEZrP12WAcUOJp5UYg4pfWL7_4WiAHWWZAoaxAb5xB+qAP4Xg@mail.gmail.com>
	<CAFzgq-ykeMeWF-ndgSm9upHTe8j6ZFYhBQjFs_WSz1oVd29j7g@mail.gmail.com>
	<CAFzgq-x+-s_Nbt4z-C4SWQbHdPr159AmL2JvpP0zg1axM+Vwcw@mail.gmail.com>
	<CABsx9T2aEvPs68pQA-KrtaDQFcTTtiB36eqKAcJRkiOFQr6WsA@mail.gmail.com>
Date: Mon, 1 Jun 2015 12:43:38 -0400
Message-ID: <CAHcfU-X2OF-YuRfBhmq3B=CqgXhqMQLYvW8T0kfCcqjS5YpAHQ@mail.gmail.com>
From: Yifu Guo <yifu@coinapex.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=001a11408c7e1841960517778704
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 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
	0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YzSvR-0001F5-IS
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
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: Mon, 01 Jun 2015 16:50:59 -0000

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

 Nielsen's Law of Internet Bandwidth is simply not true, but if you look at
data points like http://www.netindex.com/upload/ which will show we are at
least on the right track, but this is flawed still.

The fact of the matter is these speed tests are done from local origin to
local destination within the city, let alone the country ( see note about
how these test are only conducted 300 miles within the server). and our
current internet infrastructure is set up with CDNs for the web and media
consumption.
these data points can not and should not be used to model the connectivity
of a peer to peer network.

Uplink bandwidth is scarce is China and expensive, avg about $37 per 1mbps
after 5, but this is not the real problem. the true issue lies in the
ISP transparent proxy they run. this is not a problem isolated in just
China, Thailand and various other countries in Asia like Lebanon. I have
also heard in various IRCs that southern France also face this similar
issue due to poor routing configurations they have that prevents
connections to certain parts of the world, unsure if this is a mistake or a
geopolitical by-product.

As for your question earlier Gavin, from Dallas TX to a VPS in Shanghai
on =E4=B8=8A=E6=B5=B7=E7=94=B5=E4=BF=A1/Shanghai telecom, which is capped a=
t 5mbps the data results match
my concerns, I've gotten low as 83 Kbits/sec and as high as 9.24 Mbits/sec.
and other ranges in between, none are consistent. ping avg is about 250ms.

The temporary solution I recommend again from earlier is MPTCP:
http://www.multipath-tcp.org/ which allows you to multiple
interfaces/networks for a single TCP connection, this is mainly developed
for mobile3g/wifi transition but I found uses to improve bandwidth and
connection stability on the go by combining a local wifi/ethernet
connection with my 3g phone tether. this allows you to set up a middlebox
somewhere, put shadowsocks server on it, and on your local machine you can
route all TCP traffic over the shadow socks client and MPTCP will
automatically pick the best path for upload and download.



On Mon, Jun 1, 2015 at 9:59 AM, Gavin Andresen <gavinandresen@gmail.com>
wrote:

> On Mon, Jun 1, 2015 at 7:20 AM, Chun Wang <1240902@gmail.com> wrote:
>
>> I cannot believe why Gavin (who seems to have difficulty to spell my
>> name correctly.) insists on his 20MB proposal regardless the
>> community. BIP66 has been introduced for a long time and no one knows
>> when the 95% goal can be met. This change to the block max size must
>> take one year or more to be adopted. We should increase the limit and
>> increase it now. 20MB is simply too big and too risky, sometimes we
>> need compromise and push things forward. I agree with any solution
>> lower than 10MB in its first two years.
>>
>>
> Thanks, that's useful!
>
> What do other people think?  Would starting at a max of 8 or 4 get
> consensus?  Scaling up a little less than Nielsen's Law of Internet
> Bandwidth predicts for the next 20 years?  (I think predictability is
> REALLY important).
>
> I chose 20 because all of my testing shows it to be safe, and all of my
> back-of-the-envelope calculations indicate the costs are reasonable.
>
> If consensus is "8 because more than order-of-magnitude increases are
> scary" -- ok.
>
> --
> --
> Gavin Andresen
>
>
> -------------------------------------------------------------------------=
-----
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>


--=20
*Yifu Guo*
*"Life is an everlasting self-improvement."*

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

<div dir=3D"ltr"><span style=3D"font-size:12.8000001907349px">=C2=A0Nielsen=
&#39;s Law of Internet Bandwidth is simply not true, but if you look at dat=
a points like=C2=A0<a href=3D"http://www.netindex.com/upload/" target=3D"_b=
lank">http://www.netindex.com/upload/</a> which will show we are at least o=
n the right track, but this is flawed still.</span><br><div><span style=3D"=
font-size:12.8000001907349px"><br></span></div><div><span style=3D"font-siz=
e:12.8000001907349px">The fact of the matter is these speed tests are done =
from local origin to local destination within the city, let alone the count=
ry ( see note about how these test are only conducted 300 miles within the =
server). and our current internet=C2=A0infrastructure is set up with CDNs f=
or the web and media consumption.</span></div><div><span style=3D"font-size=
:12.8000001907349px">these data points can not and should not be used to mo=
del the connectivity of a peer to peer network.=C2=A0</span></div><div><spa=
n style=3D"font-size:12.8000001907349px"><br></span></div><div>Uplink bandw=
idth is scarce is China and expensive, avg about $37 per 1mbps after 5, but=
 this is not the real problem. the true issue lies in the ISP=C2=A0transpar=
ent proxy they run. this is not a problem isolated in just China, Thailand =
and various other countries in Asia like Lebanon. I have also heard in vari=
ous IRCs that southern France also face this similar issue due to poor rout=
ing configurations they have that prevents connections to certain parts of =
the world, unsure if this is a mistake or a geopolitical by-product.</div><=
div><br></div><div>As for your question earlier Gavin, from Dallas TX to a =
VPS in Shanghai on=C2=A0=E4=B8=8A=E6=B5=B7=E7=94=B5=E4=BF=A1/Shanghai telec=
om, which is capped at 5mbps the data results match my concerns, I&#39;ve g=
otten low as 83 Kbits/sec and as high as=C2=A09.24 Mbits/sec. and other ran=
ges in between, none are consistent. ping avg is about 250ms.</div><div><br=
></div><div>The temporary solution I recommend again from earlier is MPTCP:=
 <a href=3D"http://www.multipath-tcp.org/">http://www.multipath-tcp.org/</a=
> which allows you to=C2=A0multiple interfaces/networks for a single TCP co=
nnection, this is mainly developed for mobile3g/wifi transition but I found=
 uses to improve bandwidth and connection stability on the go by combining =
a local wifi/ethernet connection with my 3g phone tether. this allows you t=
o set up a middlebox somewhere, put shadowsocks server on it, and on your l=
ocal machine you can route all TCP traffic over the shadow socks client and=
 MPTCP will automatically pick the best path for upload and download.</div>=
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Mon, Jun 1, 2015 at 9:59 AM, Gavin Andresen <span dir=
=3D"ltr">&lt;<a href=3D"mailto:gavinandresen@gmail.com" target=3D"_blank">g=
avinandresen@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<span class=3D"">On Mon, Jun 1, 2015 at 7:20 AM, Chun Wang <span dir=3D"ltr=
">&lt;<a href=3D"mailto:1240902@gmail.com" target=3D"_blank">1240902@gmail.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I cannot believ=
e why Gavin (who seems to have difficulty to spell my<br>
name correctly.) insists on his 20MB proposal regardless the<br>
community. BIP66 has been introduced for a long time and no one knows<br>
when the 95% goal can be met. This change to the block max size must<br>
take one year or more to be adopted. We should increase the limit and<br>
increase it now. 20MB is simply too big and too risky, sometimes we<br>
need compromise and push things forward. I agree with any solution<br>
lower than 10MB in its first two years.<br><br></blockquote><div><br></div>=
</span><div>Thanks, that&#39;s useful!</div><div><br></div><div>What do oth=
er people think?=C2=A0 Would starting at a max of 8 or 4 get consensus?=C2=
=A0 Scaling up a little less than Nielsen&#39;s Law of Internet Bandwidth p=
redicts for the next 20 years? =C2=A0(I think predictability is REALLY impo=
rtant).</div><div><br></div><div>I chose 20 because all of my testing shows=
 it to be safe, and all of my back-of-the-envelope calculations indicate th=
e costs are reasonable.</div><div><br></div><div>If consensus is &quot;8 be=
cause more than order-of-magnitude increases are scary&quot; -- ok.</div></=
div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div>-- <br><d=
iv>--<br>Gavin Andresen<br></div>
</font></span></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
<br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><span style=3D"font-size:small;colo=
r:rgb(136,136,136)"><font face=3D"garamond, serif" size=3D"4"><b>Yifu Guo</=
b></font></span><div style=3D"font-size:small"><font face=3D"verdana, sans-=
serif"><div style=3D"font-size:13px"><font size=3D"1" color=3D"#333333"><i>=
&quot;Life is an everlasting self-improvement.&quot;</i></font></div></font=
></div></div></div>
</div>

--001a11408c7e1841960517778704--