ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

LevelDB Might Be a Great Fit for MongoDB

Mark Callaghan:

MongoDB doesn’t need multi-statement transactions. Both are limited by 1-writer or N-reader concurrency, but writes to database files are much faster with LevelDB because it doesn’t do update in place. So LevelDB doesn’t lose as much performance for IO-bound workloads by doing 1-writer or N-readers and my guess is that this could make MongoDB much better at supporting IO-bound workloads.

If getting LevelDB as a storage engine for MySQL is doubtful and I wouldn’t hold my breath until MongoDB would be using it, keep in mind that Riak might actually use LevelDB at some point.

Update: Justin Sheehy (CTO, Basho) has kindly (again) corrected me: LevelDB is supported and ships with Riak since the release of Riak 1.0. Plus it is the backend for the new secondary indexes, as it was correctly mentioned in the comments by Philip Cristiano.

Original title and link: LevelDB Might Be a Great Fit for MongoDB (NoSQL database©myNoSQL)

via: http://mysqlha.blogspot.com/2012/01/who-wants-to-write-storage-engine.html