public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Pruning in the reference client: ultraprune mode
Date: Fri, 6 Jul 2012 13:19:59 -0400	[thread overview]
Message-ID: <CAAS2fgTME9sNC6O0UnTGvNSN3ruC8P6YNVKZY-TZTVWoQi0yzA@mail.gmail.com> (raw)
In-Reply-To: <20120706165204.GA27215@vps7135.xlshosting.net>

Pieter's performance numbers are a bit conservative if anything—
profiles on ultraprune[1] show that the reference client's wasting of
a lot of time in redundant serialization and hashing operations is
the major time sink. Once thats cleared up it should be quite a
bit faster

[1] https://people.xiph.org/~greg/ultraprune_profile.png

On Fri, Jul 6, 2012 at 12:52 PM, Pieter Wuille <pieter.wuille@gmail•com> wrote:
> Also note that this is not directly related to the recent pruning
> proposals that use an alt chain with an index of unspent coins (and
> addresses), merged mined with the main chain. This could be a step
> towards such a system, however.

In particular,  if the BDB indexing in ultraprune is replaced with
a hash committed tree structure who's root is committed in the
blockchain you then have a txout commitment scheme.
Ultraprune is most of the messy structural work for that. The
rest is mostly storage differences.



      reply	other threads:[~2012-07-06 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 16:52 Pieter Wuille
2012-07-06 17:19 ` Gregory Maxwell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAS2fgTME9sNC6O0UnTGvNSN3ruC8P6YNVKZY-TZTVWoQi0yzA@mail.gmail.com \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=pieter.wuille@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox