Hi Peter, as mentioned elsewhere, one thing to point out about the new RethinkDB results is that they are using the default setting of "hard" durability from what I can tell.
Hard durability means that every individual write will wait for the data to be written to disk before the next one is run in this benchmark.
As far as I can tell, none of the other databases in this benchmark are configured to wait for disk writes. Depending on your disk and whether it's an SSD or rotational drive, this can easily result in a performance difference of 10x-1000x.
MongoDB's `safe` mode for example would be equivalent to RethinkDB's "soft" durability: Both of them acknowledge a write as soon as it has been applied to the data set in memory. However they don't wait until the data has been persisted to disk (this happens lazily in the background).
For more comparable results, I recommend running with the line `rethinkdb.db('talks').table_create('talks', durability='soft').run(conn)` which is currently commented out in your code.
Comment
Hi Peter,
as mentioned elsewhere, one thing to point out about the new RethinkDB results is that they are using the default setting of "hard" durability from what I can tell.
Hard durability means that every individual write will wait for the data to be written to disk before the next one is run in this benchmark.
As far as I can tell, none of the other databases in this benchmark are configured to wait for disk writes. Depending on your disk and whether it's an SSD or rotational drive, this can easily result in a performance difference of 10x-1000x.
MongoDB's `safe` mode for example would be equivalent to RethinkDB's "soft" durability: Both of them acknowledge a write as soon as it has been applied to the data set in memory. However they don't wait until the data has been persisted to disk (this happens lazily in the background).
For more comparable results, I recommend running with the line `rethinkdb.db('talks').table_create('talks', durability='soft').run(conn)` which is currently commented out in your code.
- Daniel @ RethinkDB