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

How not to benchmark Cassandra

The emphasis is on the not:

As Cassandra continues to increase in popularity, it’s natural that more people will benchmark it against systems they’re familiar with as part of the evaluation process. Unfortunately, many of these results are less valuable than one would hope, due to preventable errors.

While I bet every core database developer has seen a lot of irrelevant1 benchmarks — do not miss the last paragraph of the post — I still find microbencharks the most useless (i.e. 100 data points, no concurrency, no tuning => mine is bigger than yours).


  1. That’s the most polite term I could come up with. 

Original title and link: How not to benchmark Cassandra (NoSQL database©myNoSQL)

via: http://www.datastax.com/dev/blog/how-not-to-benchmark-cassandra