Engineering: Voldemort in the Wild. At kaChing, we've tried to embraced as much of the lean startup methodology as possible.
In keeping with the spirit, we've worked to scale our infrastructure smartly, using data to drive our decisions and discarding speculation. As part of our infrastructure, we've embraced Project Voldemort as a highly performant and reliable data store. One experiment we've been looking into is how the use of Solid State Drives may improve the performance of Voldemort, and perhaps even more importantly, how does that performance compare relative to the cost of the hardware. Before even starting, every indication pointed to SSD providing a significant performance boost in almost every type of benchmark, but we are solely concerned with how SSD performs in our production infrastructure.
NoSQL Live: The Dynamo Derivatives (Cassandra, Voldemort, Riak) A Benchmark for NoSQL Solutions. Sooner or later every piece of software or programming language gets benchmarked.
Some benchmarks are interesting, while others tend to be created to prove that a particular solution is better than all others (vendor benchmarks). Coming up with a fair benchmark is a hard job and trying to analyze a set of heterogenous systems is even more difficult. K.S. Bhaskar has published a benchmark proposal called ‘3n+1 NoSQL/Key-Value/Schema-Free/Schema-Less Database Benchmark’ that, in his words, is designed to allow for apples to apples comparisons of NoSQL databases using features that should allow many if not most NoSQL engines to be benchmarked. NoSQL benchmarks and performance evaluations. Some say it is the right time to start having these around.
Others are saying it’s way to early to start the “battle”. Users do want to see them and in case they’re lacking they create their own, most of the time using incomplete or wrong approaches. But what am I talking about? As some of you might have guessed already: