It's been a busy and exciting week since we announced RethinkDB. Of all the feedback we received, the most common request was for performance numbers. Before the launch our top priority was correctness. We spent most of our time testing RethinkDB with Wordpress and adding the missing features. As a result, performance suffered. In the past week we tuned the engine back up to high performance. We're still far from finished with the improvements we want to make, but we feel that we've reached a level of performance we can be proud to display.
We wrote our original benchmarking tool in Python, but during our
latest benchmarks, we noticed that it was taking about as much
time as the engine itself, hiding our real performance numbers.
We now have a very small Objective-C program (<900 lines) that
uses prepared statements in a tight loop, and times only across
the mysql_stmt_execute() call. For inserts, the
benchmark creates a …