I contributed the benchmarks to Dan's gorethink driver. Dan is great to collaborate with so if you want to hack on Go and contribute to OSS, consider giving his

I contributed the benchmarks to Dan's gorethink driver. Dan is great to collaborate with so if you want to hack on Go and contribute to OSS, consider giving his project a look. One way to improve writes is to batch them, an example is here. https://github.com/dancannon/gorethink/blob/master/benchmarks_test.go#L15-L43 https://github.com/dancannon/gorethink/blob/master/benchmark... I believe rethinkdb docs state that 200 is the optimum batch size. Another way is to enable the soft durability mode. http://rethinkdb.com/api/javascript/insert/ http://rethinkdb.com/api/javascript/insert/ "In soft durability mode RethinkDB will acknowledge the write immediately after receiving and caching it, but before the write has been committed to disk." https://github.com/dancannon/gorethink/blob/master/benchmarks_test.go#L79-L114 https://github.com/dancannon/gorethink/blob/master/benchmark... Obviously your business requirements come into play. I prefer the Hard writes because my data is important to me but I do insert debug messages using soft writes in one application I have. *Edit: Heh I forgot to mention, on my Macbook Pro I was getting 20k w/s while batching and using soft writes. Individual writes for me are hovering around 10k w/s on the 8 cpu 24gb instance i have. But yeah, define your business reqs then write your own benchmarks and see if the need is met. Many devs write benchmarks in order to be the fastest and not the correctest. Super lame.