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 irrelevant 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).
Original title and link: How not to benchmark Cassandra