From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SnCCP-0008V6-9O for bitcoin-development@lists.sourceforge.net; Fri, 06 Jul 2012 17:20:09 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=gmaxwell@gmail.com; helo=mail-gg0-f175.google.com; Received: from mail-gg0-f175.google.com ([209.85.161.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SnCCL-0002Bf-8z for bitcoin-development@lists.sourceforge.net; Fri, 06 Jul 2012 17:20:09 +0000 Received: by ggnp4 with SMTP id p4so9019812ggn.34 for ; Fri, 06 Jul 2012 10:19:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.190.97 with SMTP id gp1mr38914145pbc.76.1341595199440; Fri, 06 Jul 2012 10:19:59 -0700 (PDT) Received: by 10.68.59.6 with HTTP; Fri, 6 Jul 2012 10:19:59 -0700 (PDT) In-Reply-To: <20120706165204.GA27215@vps7135.xlshosting.net> References: <20120706165204.GA27215@vps7135.xlshosting.net> Date: Fri, 6 Jul 2012 13:19:59 -0400 Message-ID: From: Gregory Maxwell To: Pieter Wuille Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.8 (/) 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 (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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.8 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SnCCL-0002Bf-8z Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Pruning in the reference client: ultraprune mode X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2012 17:20:09 -0000 Pieter's performance numbers are a bit conservative if anything=E2=80=94 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 wr= ote: > 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.