From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Faster databases than LevelDB
Date: Tue, 17 Sep 2013 13:00:04 +0200 [thread overview]
Message-ID: <CANEZrP1ksdGfB-282giysF-2Lo==NiD-nBdon5FJ9wLBLmX=TA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
LevelDB is fast - very fast if you give it enough CPU time and disk seeks.
But it's not the last word in performance.
HyperLevelDB is a forked LevelDB with some changes, mostly, finer grained
locking and changes to how compaction works:
http://hyperdex.org/performance/leveldb/
However, it comes with a caveat - one of the changes they made is to take
away write throttling if compaction falls behind, the app itself is
expected to do that.
Sophia is a competitor to LevelDB. The website claims that in benchmarks it
completely smokes LevelDB. I have not explored how it does this or tried to
replicate their benchmarks myself:
http://sphia.org/index.html
http://sphia.org/benchmarks.html
It's written in C and BSD licensed.
As an example of the kind of speedup they claim to be capable of, they say
LevelDB could do 167,476 random reads per second on their SSD based
machine. Sophia could do 438,084 reads/sec. Random reads are of course the
most interesting for us because that's what UTXO lookups involve.
They also compare against HyperLevelDB, where the differences are much less
pronounced and actually HyperLevelDB appears to be able to do random writes
faster than Sophia.
[-- Attachment #2: Type: text/html, Size: 1623 bytes --]
next reply other threads:[~2013-09-17 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 11:00 Mike Hearn [this message]
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
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='CANEZrP1ksdGfB-282giysF-2Lo==NiD-nBdon5FJ9wLBLmX=TA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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