This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.


Stefan Tilkov,

MemcacheDB sounds interesting:

MemcacheDB is a distributed key-value storage system designed for persistent. It is NOT a cache solution, but a persistent storage engine for fast and reliable key-value based object storage and retrieval. It conforms to memcache protocol(not completed, see below), so any memcached client can have connectivity with it. MemcacheDB uses Berkeley DB as a storing backend, so lots of features including transaction and replication are supported.

[via Holger Arendt]

On January 8, 2009 10:46 AM, Hynek (Pichi) Vychodil said:

Impressive benchmark in first sight but in second … There are only 8 concurrent clients. What happen if there come more, may be ten thousand? There are used four thread but I can’t determine how much CPU is in the box, assume one (does not scale 23k vs 18k reads/s and 44k vs 64k write/s), but how it scale on more CPU’s?

You mentioned transaction support, but there is not any on API. Transactions are used only for communication between MemcachedDB and Berkeley DB. API just provide some higher atomic operations which using backend transaction ability.

It doesn’t look so impressive in detailed view.

On January 8, 2009 10:53 AM, Hynek (Pichi) Vychodil said:

It goes worse, testing HW is dual core. Scaling gain is only 44%. Those are bad news.