From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Faster databases than LevelDB
Date: Tue, 17 Sep 2013 06:20:13 -0700 [thread overview]
Message-ID: <CAAS2fgSqnc_0mWFrt9TREhZzF+JGJZxs_XD_ht+6nngFE_oE3w@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP1ksdGfB-282giysF-2Lo==NiD-nBdon5FJ9wLBLmX=TA@mail.gmail.com>
On Tue, Sep 17, 2013 at 4:00 AM, Mike Hearn <mike@plan99.net> wrote:
> LevelDB is fast - very fast if you give it enough CPU time and disk seeks.
> But it's not the last word in performance.
I'd looked at the hyperleveldb, but their performance graphs made it
seem like it would be slower for the actual database sizes we're using
today.
Is there a competitor that specializes in being more robust to corruption? :(
next prev parent reply other threads:[~2013-09-17 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 11:00 [Bitcoin-development] Faster databases than LevelDB Mike Hearn
2013-09-17 11:41 ` Jorge Timón
2013-09-17 11:45 ` Mike Hearn
2013-09-17 13:48 ` Jorge Timón
2013-09-17 13:20 ` Gregory Maxwell [this message]
2013-09-17 17:08 ` Mark Friedenbach
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=CAAS2fgSqnc_0mWFrt9TREhZzF+JGJZxs_XD_ht+6nngFE_oE3w@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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