summaryrefslogtreecommitdiff
path: root/3a/62c157afcdb317fa7b098c6b1daacd65dd1111
blob: 6010e3a47180a4097a25aa659b956ebb0d3d8fe7 (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
Return-Path: <admin@glados.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 98C7F268
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 10 Nov 2015 01:59:02 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com
	[209.85.160.182])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D00AF8C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 10 Nov 2015 01:59:01 +0000 (UTC)
Received: by ykdv3 with SMTP id v3so205573714ykd.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 09 Nov 2015 17:59:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=glados_cc.20150623.gappssmtp.com; s=20150623;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=z90xfCln9MKLlZU8g2hbPsprNfbRXbHaDlo/44IkC7Q=;
	b=NH/T0kVgcARsUvyeYGJWcchAP8g0n+1TiSIVmE+y07Je4Ym9/6DxhSlwtQ+Tk2DSCi
	OalPtTlgkpPdzry99sCDYJqIIdiRGvdK2sSxDgCx57EXYgvex7uBtvceNuodU4DiChth
	Lx0D/YMerDVyu03uMUqtzoQtM7gvG5EUjg5qtIZpSwGZ+J3feAvY1kSkGaUxRQLDdSMN
	OSauV37EOyLjA7JoTFKn4qns0TunkN3wzvxT3GZvDLYnJmkhtNQMKldHPMF7ODGJSeHe
	+8cjML2+1VA65WnukJcaoRZYI18dVVjJdsI13hP6GEsFIKhcsJmaDLCamrP+ZyQjyze7
	/bDg==
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:from:date
	:message-id:subject:to:cc:content-type;
	bh=z90xfCln9MKLlZU8g2hbPsprNfbRXbHaDlo/44IkC7Q=;
	b=DslroqV5u9wxE9mVzkOjIxOVN1x/Mv36UV4gpFPbE5pkDMLjZyicZk+9kW+EN0ATUX
	A8om06m2AFYp8SImm+9nkA6u6lBQJNDP+ttg850zcj0sJMyG/WNvdCdLFrk84bdNtzdi
	OO+TnjH7C9vdH966OYqnpn1/CWaUypOS2laQ59BI6OB8fw6QIuGD+s8mBLM1ObMuoa7L
	SFPkt2t1BIKWmMv8b7687SWzjsWub0o6sK+jDTTiY2aYCncfZXFaA/pE8qN8yTX9CUlJ
	adPqdQ63PbQwnsF14rpBWm8ZZRD708cRTkDzuxX0+lJt2AAvvrfjEhif7NSFkC8cZmgG
	s92w==
X-Gm-Message-State: ALoCoQlE5/TPwHJEUMltRCG+Y2lj0vnZ5q5gyWrlVz0QX2Rmw2cgIMBDn3xGB7ca20ek7RsGVMWc
X-Received: by 10.13.228.65 with SMTP id n62mr881672ywe.302.1447120741055;
	Mon, 09 Nov 2015 17:59:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.224.135 with HTTP; Mon, 9 Nov 2015 17:58:41 -0800 (PST)
X-Originating-IP: [64.213.30.122]
In-Reply-To: <20151109210449.GE5886@mcelrath.org>
References: <5640F172.3010004@gmail.com> <20151109210449.GE5886@mcelrath.org>
From: gladoscc <admin@glados.cc>
Date: Tue, 10 Nov 2015 12:58:41 +1100
Message-ID: <CAL7-sS0Apm4O_Qi0FmY7=H580rEVD6DYjk2y+ACpZmKqUJTQwA@mail.gmail.com>
To: Bob McElrath <bob_bitcoin@mcelrath.org>
Content-Type: multipart/alternative; boundary=94eb2c030c10b7eecf0524260de0
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 10 Nov 2015 01:59:33 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] request BIP number for: "Support for Datastream
	Compression"
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 01:59:02 -0000

--94eb2c030c10b7eecf0524260de0
Content-Type: text/plain; charset=UTF-8

I think 25% bandwidth savings is certainly considerable, especially for
people running full nodes in countries like Australia where internet
bandwidth is lower and there are data caps.

I absolutely would not dismiss 25% compression. gzip and bzip2 compression
is relatively standard, and I'd consider the point of implementation
complexity tradeoff to be somewhere along 5-10%.

On Tue, Nov 10, 2015 at 8:04 AM, Bob McElrath via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I would expect that since a block contains mostly hashes and crypto
> signatures,
> it would be almost totally incompressible.  I just calculated compression
> ratios:
>
> zlib    -15%    (file is LARGER)
> gzip     28%
> bzip2    25%
>
> So zlib compression is right out.  How much is ~25% bandwidth savings
> worth to
> people?  This seems not worth it to me.  :-/
>
> Peter Tschipper via bitcoin-dev [bitcoin-dev@lists.linuxfoundation.org]
> wrote:
> > This is my first time through this process so please bear with me.
> >
> > I opened a PR #6973 this morning for Zlib Block Compression for block
> > relay and at the request of @sipa  this should have a BIP associated
> > with it.   The idea is simple, to compress the datastream before
> > sending, initially for blocks only but it could theoretically be done
> > for transactions as well.  Initial results show an average of 20% block
> > compression and taking 90 milliseconds for a full block (on a very slow
> > laptop) to compress.  The savings will be mostly in terms of less
> > bandwidth used, but I would expect there to be a small performance gain
> > during the transmission of the blocks particularly where network latency
> > is higher.
> >
> > I think the BIP title, if accepted should be the more generic, "Support
> > for Datastream Compression"  rather than the PR title of "Zlib
> > Compression for block relay" since it could also be used for
> > transactions as well at a later time.
> >
> > Thanks for your time...
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> >
> > !DSPAM:5640ff47206804314022622!
> --
> Cheers, Bob McElrath
>
> "For every complex problem, there is a solution that is simple, neat, and
> wrong."
>     -- H. L. Mencken
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">I think 25% bandwidth savings is certainly considerable, e=
specially for people running full nodes in countries like Australia where i=
nternet bandwidth is lower and there are data caps.<div><br></div><div>I ab=
solutely would not dismiss 25% compression. gzip and bzip2 compression is r=
elatively standard, and I&#39;d consider the point of implementation comple=
xity tradeoff to be somewhere along 5-10%.=C2=A0</div></div><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Tue, Nov 10, 2015 at 8:04 AM,=
 Bob McElrath via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitco=
in-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linux=
foundation.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I wo=
uld expect that since a block contains mostly hashes and crypto signatures,=
<br>
it would be almost totally incompressible.=C2=A0 I just calculated compress=
ion ratios:<br>
<br>
zlib=C2=A0 =C2=A0 -15%=C2=A0 =C2=A0 (file is LARGER)<br>
gzip=C2=A0 =C2=A0 =C2=A028%<br>
bzip2=C2=A0 =C2=A0 25%<br>
<br>
So zlib compression is right out.=C2=A0 How much is ~25% bandwidth savings =
worth to<br>
people?=C2=A0 This seems not worth it to me.=C2=A0 :-/<br>
<span class=3D""><br>
Peter Tschipper via bitcoin-dev [<a href=3D"mailto:bitcoin-dev@lists.linuxf=
oundation.org">bitcoin-dev@lists.linuxfoundation.org</a>] wrote:<br>
</span><div><div class=3D"h5">&gt; This is my first time through this proce=
ss so please bear with me.<br>
&gt;<br>
&gt; I opened a PR #6973 this morning for Zlib Block Compression for block<=
br>
&gt; relay and at the request of @sipa=C2=A0 this should have a BIP associa=
ted<br>
&gt; with it.=C2=A0 =C2=A0The idea is simple, to compress the datastream be=
fore<br>
&gt; sending, initially for blocks only but it could theoretically be done<=
br>
&gt; for transactions as well.=C2=A0 Initial results show an average of 20%=
 block<br>
&gt; compression and taking 90 milliseconds for a full block (on a very slo=
w<br>
&gt; laptop) to compress.=C2=A0 The savings will be mostly in terms of less=
<br>
&gt; bandwidth used, but I would expect there to be a small performance gai=
n<br>
&gt; during the transmission of the blocks particularly where network laten=
cy<br>
&gt; is higher.<br>
&gt;<br>
&gt; I think the BIP title, if accepted should be the more generic, &quot;S=
upport<br>
&gt; for Datastream Compression&quot;=C2=A0 rather than the PR title of &qu=
ot;Zlib<br>
&gt; Compression for block relay&quot; since it could also be used for<br>
&gt; transactions as well at a later time.<br>
&gt;<br>
&gt; Thanks for your time...<br>
&gt; _______________________________________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
&gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
&gt;<br>
&gt;<br>
</div></div>&gt; !DSPAM:5640ff47206804314022622!<br>
--<br>
Cheers, Bob McElrath<br>
<br>
&quot;For every complex problem, there is a solution that is simple, neat, =
and wrong.&quot;<br>
=C2=A0 =C2=A0 -- H. L. Mencken<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>

--94eb2c030c10b7eecf0524260de0--