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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <arklan.uthoslin@gmail.com>) id 1TPkUo-0007UE-14
for bitcoin-development@lists.sourceforge.net;
Sun, 21 Oct 2012 01:38:30 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=arklan.uthoslin@gmail.com;
helo=mail-vb0-f47.google.com;
Received: from mail-vb0-f47.google.com ([209.85.212.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TPkUn-0004fA-1g
for bitcoin-development@lists.sourceforge.net;
Sun, 21 Oct 2012 01:38:29 +0000
Received: by mail-vb0-f47.google.com with SMTP id ez10so1887158vbb.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 20 Oct 2012 18:38:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.211.37 with SMTP id mz5mr8748303vec.30.1350783503541; Sat,
20 Oct 2012 18:38:23 -0700 (PDT)
Received: by 10.220.137.139 with HTTP; Sat, 20 Oct 2012 18:38:23 -0700 (PDT)
In-Reply-To: <CAPg+sBjh0CTYHTZovg=wzy=YJTRwoci3QDJO=qO2kV8wQnndnA@mail.gmail.com>
References: <CAPg+sBjh0CTYHTZovg=wzy=YJTRwoci3QDJO=qO2kV8wQnndnA@mail.gmail.com>
Date: Sat, 20 Oct 2012 19:38:23 -0600
Message-ID: <CAGg41SUnw=KDxmeE7sXO-x1qSsVUsf27HKqvNP3R0D654LbqkA@mail.gmail.com>
From: Arklan Uth Oslin <arklan.uthoslin@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6bf2ee5a4db04cc87cae2
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
(arklan.uthoslin[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: 1TPkUn-0004fA-1g
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Ultraprune merged in mainline
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: Sun, 21 Oct 2012 01:38:30 -0000
--047d7bd6bf2ee5a4db04cc87cae2
Content-Type: text/plain; charset=ISO-8859-1
i can happily start testing this this weekend. however i'm not 100% sure
how to get a copy. i looked around github, but wasn't sure which was the
proper project. could i get a link and a simple "do this, this and this"?
thanks.
i feel like a newb. ugh.
Arklan
----------
As long as there is light, the darkness holds no fear. And yet, even in the
deepest black, there is life. - Arklan Uth Oslin
I want to leave this world the same way I came into it: backwards and on
fire. - Arklan Uth Oslin
On Sat, Oct 20, 2012 at 4:33 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
> Hello everyone,
>
> I've just merged my "ultraprune" branch into mainline (including
> Mike's LevelDB work). This is a very significant change, and all
> testing is certainly welcome. As a result of this, many pull requests
> probably don't apply cleanly anymore. If you need help rebasing them
> on the new structure, ask me.
>
> The idea behind ultraprune is to use an ultra-pruned copy (only
> unspent transaction outputs in a custom compact format) of the block
> chain for validation (as opposed to a transaction index into the block
> chain). It still keeps all blocks around for serving them to other
> nodes, for rescanning, and for reorganisations. As such, it is still a
> full node. So, despite the name, it does not implement any actual
> pruning yet, though pruning would be trivial to implement now. This
> would have profound effects on the network though, so may still need
> some discussion first.
>
> A small summary of the changes:
> * Instead of blk000?.dat, we have blocks/blk000??.dat files of max
> 128 MiB, pre-allocated per 16 MiB
> * Instead of a Berklely DB blkindex.dat, we have a LevelDB directory
> blktree/. This only contains a block index, no transaction index.
> * A new LevelDB directory coins/, which contains data about the
> current unspent transaction output set.
> * New files blocks/rev000??.dat contain undo data for blocks
> (necessary for reorganisation).
> * More information is kept about blocks and block files, so
> facilitate pruning in the future, and to prepare for a headers-first
> mode.
> * Two new RPC calls are added: gettxout and gettxoutsetinfo.
>
> The most noticeable change should be performance: LevelDB deals much
> better with slow I/O than BDB does, and the working set size for
> validation is an order of magnitude smaller. In the longer run, I
> think it is an evolution towards separation between validation nodes
> and archive nodes, which is needed in my opinion.
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bd6bf2ee5a4db04cc87cae2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
i can happily start testing this this weekend. however i'm not 100% sur=
e how to get a copy. i looked around github, but wasn't sure which was =
the proper project. could i get a link and a simple "do this, this and=
this"? thanks.<div>
<br></div><div>i feel like a newb. ugh.<br clear=3D"all"><div>=A0</div>
<div>Arklan<br><br>----------<br>
<div>As long as there is light, the darkness holds no fear. And yet, even i=
n the deepest black, there is life. - Arklan Uth Oslin</div></div>
<div>=A0</div>
<div>I want to leave this world the same way I came into it: backwards and =
on fire. - Arklan Uth Oslin</div><br>
<br><br><div class=3D"gmail_quote">On Sat, Oct 20, 2012 at 4:33 PM, Pieter =
Wuille <span dir=3D"ltr"><<a href=3D"mailto:pieter.wuille@gmail.com" tar=
get=3D"_blank">pieter.wuille@gmail.com</a>></span> wrote:<br><blockquote=
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
Hello everyone,<br>
<br>
I've just merged my "ultraprune" branch into mainline (includ=
ing<br>
Mike's LevelDB work). This is a very significant change, and all<br>
testing is certainly welcome. As a result of this, many pull requests<br>
probably don't apply cleanly anymore. If you need help rebasing them<br=
>
on the new structure, ask me.<br>
<br>
The idea behind ultraprune is to use an ultra-pruned copy (only<br>
unspent transaction outputs in a custom compact format) of the block<br>
chain for validation (as opposed to a transaction index into the block<br>
chain). It still keeps all blocks around for serving them to other<br>
nodes, for rescanning, and for reorganisations. As such, it is still a<br>
full node. So, despite the name, it does not implement any actual<br>
pruning yet, though pruning would be trivial to implement now. This<br>
would have profound effects on the network though, so may still need<br>
some discussion first.<br>
<br>
A small summary of the changes:<br>
=A0* Instead of blk000?.dat, we have blocks/blk000??.dat files of max<br>
128 MiB, pre-allocated per 16 MiB<br>
=A0* Instead of a Berklely DB blkindex.dat, we have a LevelDB directory<br>
blktree/. This only contains a block index, no transaction index.<br>
=A0* A new LevelDB directory coins/, which contains data about the<br>
current unspent transaction output set.<br>
=A0* New files blocks/rev000??.dat contain undo data for blocks<br>
(necessary for reorganisation).<br>
=A0* More information is kept about blocks and block files, so<br>
facilitate pruning in the future, and to prepare for a headers-first<br>
mode.<br>
=A0* Two new RPC calls are added: gettxout and gettxoutsetinfo.<br>
<br>
The most noticeable change should be performance: LevelDB deals much<br>
better with slow I/O than BDB does, and the working set size for<br>
validation is an order of magnitude smaller. In the longer run, I<br>
think it is an evolution towards separation between validation nodes<br>
and archive nodes, which is needed in my opinion.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Pieter<br>
<br>
---------------------------------------------------------------------------=
---<br>
Everyone hates slow websites. So do we.<br>
Make your web apps faster with AppDynamics<br>
Download AppDynamics Lite for free today:<br>
<a href=3D"http://p.sf.net/sfu/appdyn_sfd2d_oct" target=3D"_blank">http://p=
.sf.net/sfu/appdyn_sfd2d_oct</a><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>
</font></span></blockquote></div><br></div>
--047d7bd6bf2ee5a4db04cc87cae2--
|