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



A Very Specific Benchmark: Files vs MySQL vs Memcached vs Redis vs MongoDB

This sort of very specific benchmarks are valid/interesting if and only if:

  • they simulate extremely close the real life scenario that will be supported by the final application
  • they are not generalized to compare the overall performance of the NoSQL stores
  • the NoSQL store is correctly configured to fulfill the app requirements (f.e. durability)
  • it is understood that the driver has an impact on the results

In this case the benchmark measured requests/s for a usecase of session storage for a Tornado-based web app. You can see the results below:

Reference MySQL Memcached MongoDB Redis
1626 req/s 1353 req/s 1473 req/s 1582 req/s 1418 req/s

Note: The benchmark doesn’t provide enough details about the drivers used.