diff options
author | Mike Hearn <mike@plan99.net> | 2012-06-19 11:05:20 +0200 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2012-06-19 09:05:28 +0000 |
commit | 8eb6451f55fb09c5850105a765d4803a59848b5d (patch) | |
tree | a6196caf3b21aad7315952962d5b9cc0b48f786d | |
parent | c00deafcc8e77099b443c1b8ce6bcc223dd17e6c (diff) | |
download | pi-bitcoindev-8eb6451f55fb09c5850105a765d4803a59848b5d.tar.gz pi-bitcoindev-8eb6451f55fb09c5850105a765d4803a59848b5d.zip |
Re: [Bitcoin-development] LevelDB benchmarking
-rw-r--r-- | 1c/dd7646e20757e89fa4ae0f7959e97fe315e135 | 93 |
1 files changed, 93 insertions, 0 deletions
diff --git a/1c/dd7646e20757e89fa4ae0f7959e97fe315e135 b/1c/dd7646e20757e89fa4ae0f7959e97fe315e135 new file mode 100644 index 000000000..c1bab294a --- /dev/null +++ b/1c/dd7646e20757e89fa4ae0f7959e97fe315e135 @@ -0,0 +1,93 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <mh.in.england@gmail.com>) id 1SguNM-0000w3-8o + for bitcoin-development@lists.sourceforge.net; + Tue, 19 Jun 2012 09:05:28 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 74.125.82.175 as permitted sender) + client-ip=74.125.82.175; envelope-from=mh.in.england@gmail.com; + helo=mail-we0-f175.google.com; +Received: from mail-we0-f175.google.com ([74.125.82.175]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1SguNL-0005KH-DU + for bitcoin-development@lists.sourceforge.net; + Tue, 19 Jun 2012 09:05:28 +0000 +Received: by werg55 with SMTP id g55so4851846wer.34 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 19 Jun 2012 02:05:21 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.216.143.213 with SMTP id l63mr10360162wej.117.1340096720471; + Tue, 19 Jun 2012 02:05:20 -0700 (PDT) +Sender: mh.in.england@gmail.com +Received: by 10.216.254.232 with HTTP; Tue, 19 Jun 2012 02:05:20 -0700 (PDT) +In-Reply-To: <CAAS2fgTNqUeYy+oEFyQWrfs4Xyb=3NXutvCmLusknF-18JmFQg@mail.gmail.com> +References: <CANEZrP2xnsOHyH+a1g6qSNSx_g+TW-yvL0Due7PVr421U6kRLw@mail.gmail.com> + <CAAS2fgTNqUeYy+oEFyQWrfs4Xyb=3NXutvCmLusknF-18JmFQg@mail.gmail.com> +Date: Tue, 19 Jun 2012 11:05:20 +0200 +X-Google-Sender-Auth: qPJFo8antv3m-CZsJpx0DvIIjlA +Message-ID: <CANEZrP2q9a_0rFh+oo6iUFF1goWs0OJO1xPvxC9zqNA-6VnFAQ@mail.gmail.com> +From: Mike Hearn <mike@plan99.net> +To: Gregory Maxwell <gmaxwell@gmail.com>, + Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable +X-Spam-Score: -1.5 (-) +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 + (mh.in.england[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 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 +X-Headers-End: 1SguNL-0005KH-DU +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: Tue, 19 Jun 2012 09:05:28 -0000 + ++list + +On Mon, Jun 18, 2012 at 9:07 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote= +: +> In addition to the ECDSA caching, =C2=A0ECDSA can can easily be run on +> multiple cores for basically a linear speedup.. so even with the +> checking in place once ECDSA was using multiple threads we'd be back +> to the DB being the bottleneck for this kind of case. + +Maybe ... looking again I think I may be wrong about being IO bound in +the last benchmark. The core running the main Bitcoin thread is still +pegged and the LevelDB background thread is only spending around 20% +of its time in iowait. An oprofile shows most of the time being spent +inside a std::map. + +OK, to make progress on this work I need a few decisions (Gavin?) + +1) Shall we do it? + +2) LevelDB is obscure, new and has a very minimalist build system. It +supports "make" but not "make install", for example, and is unlikely +to be packaged. It's also not very large. I suggest we just check the +source into the main Bitcoin tree and link it statically rather than +complicate the build. + +3) As the DB format would change and a slow migration period +necessary, any other tweaks to db format we could make at the same +time? Right now the key/values are the same as before, though using +satoshi serialization for everything is a bit odd. + +We'd need UI for migration as well. + + |