which keyvalue store has the best performance? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. 开发者_运维技巧

---

Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.

Closed 9 years ago.

Improve this question

I think tow months ago. I found a google's open source project that can store key value pairs with high performance. But i forget the name. Could anybody tell me? or you can have some other suggestions for me? I have been using BerkerlyDB, but I found BerkerlyDb is not fast enough for my program. However, berkerylyDB is convenient to use as it appears as a java lib jar, which can be integraed with my program seamlessly. My program is also written in Java.

---

Two strong competitors in the DHT (Distributed Hash Table) 'market':

• Cassandra (created by Facebook, in use by Digg and Twitter)
• HBase

Here is a presentation about Cassandra. On slide 20 you'll see some speed benchmarks- 0.12 ms / write
(You can search around for the whole presentation, including Eric Evans talking)

---

Nobody mentions leveldb and yet this post is at the top when searching for "good key value store". Leveldb in my experience is simply awesome. It's so fast I couldn't believe it. I've been trying quite a few databases for a task I was doing. I tried:

• windows azure table storage (expensive, value size max 1 Mb and each property size is max 64 Kb)
• redis (awesome if you have as much ram as you please)
• mongodb (awesome as long as there is enough ram, breaks after that point)
• sql server (expensive, needs maintenance, such as rebuilding indexes and eventually still not fast enough)
• sqlite (free, but not as simple to use as leveldb and not fast)
• leveldb. If you can model your job as to reading large consecutive chunks of data through an iterator then you'll get great speed. Writing is also pretty fast. Combine it with ssd disk and you'll love it.

---

Bigtable?

---

Redis

http://code.google.com/p/redis/

---

Maybe you should describe what features you need. If it doesn't need to be distributed (does it?) then I would try using the H2 Database. For those who think "it can't be fast because it's using SQL" please note that when using prepared statement, SQL parsing is only done once. Disclaimer: I'm the main author of H2.

---

Many answer seem to automatically assume need for distribution; but that seems odd if question refers to BDB.

With that in mind, beyond Redis and H2 (which are both good), there is also Tokyo Cabinet to consider, which seems to offer benefits over BDB. And one more newer possibility is Krati.

---

I think you saw Guava or Google collections.