I've been playing around with Rethink for a couple of days now, and I just can't get over how nice the admin web UI is. Scaling up machines is quick and easy, and it's pretty simple to resolve master/secondary issues when one of the servers goes down (or it's shut off).
I'm seeing some performance issues, and I'm definitely going to spend some time messing with my test data and optimizing it for Rethink. Right now, a couple of basic counting queries take ~1 second when the MySQL equivalent takes milliseconds. The other issue I'm having is that I simply did an import of existing data from MySQL that contains dates, which are treated as strings, so I'll need to convert the dates into a native format (integer based timestamps) before I can get some more performance numbers.
Keep us posted on the performance issues you experience-- the team hangs out on IRC (#rethinkdb on freenode) and are usually more than happy to help work through these problems. If you identify a specific query that isn't performant, please open an issue on Github as well (http://rethinkdb.com/docs/comparison-tables/).
Anyway timestamps are better. First reason is difference in implementations of "date"-formats in almost each database, and second reason - integers will always faster than strings or structures.
I'm seeing some performance issues, and I'm definitely going to spend some time messing with my test data and optimizing it for Rethink. Right now, a couple of basic counting queries take ~1 second when the MySQL equivalent takes milliseconds. The other issue I'm having is that I simply did an import of existing data from MySQL that contains dates, which are treated as strings, so I'll need to convert the dates into a native format (integer based timestamps) before I can get some more performance numbers.