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; 
MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Ultraprune merged in mainline
Precedence: list

--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&#39;m not 100% sur=
e how to get a copy. i looked around github, but wasn&#39;t sure which was =
the proper project. could i get a link and a simple &quot;do this, this and=
 this&quot;? 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">&lt;<a href=3D"mailto:pieter.wuille@gmail.com" tar=
get=3D"_blank">pieter.wuille@gmail.com</a>&gt;</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&#39;ve just merged my &quot;ultraprune&quot; branch into mainline (includ=
ing<br>
Mike&#39;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&#39;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--