My experience was pretty much the opposite, especially for timeseries data the sequential scan performance of Rethink was pretty bad, especially when you add filters, grouping etc. Postgres gives me about 3-10x the speed.

And that takes into consideration that Rethink uses all cores and Postgres only one. Plus I used jsonb in Postgres to make it totally fair.

And on top I encountered really inconsistent performance. For example when you access a field of an object that doesn't exist, it apparently raises internally an exception and that slows things down a lot. But you don't really see this.

I get it that Rethink is trying to distinguish itself from the other players and find a nice niche for itself but I really wish they improved on the performance and while at it removed the limitation of 32 servers in a cluster.

Oh and the huge blow up of data on disk also needs a lot of work. Rethink used about 5x more disk space in my trials for a table with about 10 million rows. With fewer indexes than PG.

I really like the ops simplicity of Rethink, especially when it comes to clustering. So I have high hopes for it.