From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1ShJES-0003zD-5a for bitcoin-development@lists.sourceforge.net; Wed, 20 Jun 2012 11:37:56 +0000 X-ACL-Warn: Received: from vps7135.xlshosting.net ([178.18.90.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1ShJEP-0003s6-V2 for bitcoin-development@lists.sourceforge.net; Wed, 20 Jun 2012 11:37:56 +0000 Received: by vps7135.xlshosting.net (Postfix, from userid 1000) id C2562618E8; Wed, 20 Jun 2012 13:37:46 +0200 (CEST) Date: Wed, 20 Jun 2012 13:37:46 +0200 From: Pieter Wuille To: Mike Hearn Message-ID: <20120620113744.GA14695@vps7135.xlshosting.net> References: <4FE0D167.7030506@justmoon.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1ShJEP-0003s6-V2 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] LevelDB benchmarking 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: Wed, 20 Jun 2012 11:37:56 -0000 On Wed, Jun 20, 2012 at 11:44:48AM +0200, Mike Hearn wrote: > Also, Satoshis code does use ordered access/iteration in at least one > place, where it looks up the "owner transactions" of a tx. I'm not > totally sure what that code is used for, but it's there. Whether it's > actually the best way to solve the problem is another question :-) Two days ago on #bitcoin-dev: 21:01:19< sipa> what was CTxDB::ReadOwnerTxes ever used for? 21:01:31< sipa> maybe it predates the wallet logic (read: it's not used anywhere in the code, and apparently wasn't ever, even in 0.1.5) -- Pieter