diff options
| author | Pieter Wuille <pieter.wuille@gmail.com> | 2012-06-20 13:37:46 +0200 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2012-06-20 11:37:56 +0000 |
| commit | b1a9446b724058fe08ed9f4a532bcfa2e2e837ff (patch) | |
| tree | 084b97ed71a741841fcccbb1daf19b01b1ddac84 /6a/2ee6071a7141e9f30ad09cec553861e27e3a42 | |
| parent | e3bffe289f2245425e1d224ba39360e74595e462 (diff) | |
| download | pi-bitcoindev-b1a9446b724058fe08ed9f4a532bcfa2e2e837ff.tar.gz pi-bitcoindev-b1a9446b724058fe08ed9f4a532bcfa2e2e837ff.zip | |
Re: [Bitcoin-development] LevelDB benchmarking
Diffstat (limited to '6a/2ee6071a7141e9f30ad09cec553861e27e3a42')
| -rw-r--r-- | 6a/2ee6071a7141e9f30ad09cec553861e27e3a42 | 73 |
1 files changed, 73 insertions, 0 deletions
diff --git a/6a/2ee6071a7141e9f30ad09cec553861e27e3a42 b/6a/2ee6071a7141e9f30ad09cec553861e27e3a42 new file mode 100644 index 000000000..218dd71d5 --- /dev/null +++ b/6a/2ee6071a7141e9f30ad09cec553861e27e3a42 @@ -0,0 +1,73 @@ +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 <pw@vps7135.xlshosting.net>) 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 <pieter.wuille@gmail.com> +To: Mike Hearn <mike@plan99.net> +Message-ID: <20120620113744.GA14695@vps7135.xlshosting.net> +References: <CANEZrP2xnsOHyH+a1g6qSNSx_g+TW-yvL0Due7PVr421U6kRLw@mail.gmail.com> + <CAAS2fgTNqUeYy+oEFyQWrfs4Xyb=3NXutvCmLusknF-18JmFQg@mail.gmail.com> + <CANEZrP2q9a_0rFh+oo6iUFF1goWs0OJO1xPvxC9zqNA-6VnFAQ@mail.gmail.com> + <CABsx9T3pQFqL0xsvRfnixYEATO61qMCCDdLmtqZkbVLW0Vxytg@mail.gmail.com> + <CANEZrP08NrCJM2gxNitXrLjuY6AusNULvkcheN_0MbgFQV_QXw@mail.gmail.com> + <4FE0D167.7030506@justmoon.de> + <CANEZrP3WHA7P+t2Jk+w1kBMk0QuqN+gBXeNMoAnj_rK=nor-qg@mail.gmail.com> +MIME-Version: 1.0 +Content-Type: text/plain; charset=us-ascii +Content-Disposition: inline +In-Reply-To: <CANEZrP3WHA7P+t2Jk+w1kBMk0QuqN+gBXeNMoAnj_rK=nor-qg@mail.gmail.com> +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: <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: 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 + + + |