3 ms·
(Ozgun from Citus Data here.) We're going to publish more comprehensive results in a few weeks. In our initial tests, we found the speed up to depend a lot on
by ozgune 13y ago
(Ozgun from Citus Data here.)
We're going to publish more comprehensive results in a few weeks. In our initial tests, we found the speed up to depend a lot on the underlying data and the type of queries.
For example, we found that when compression reduced the working set from being on disk to in-memory, there was a significant jump.
Also, we're looking to do optimizations on the cost estimation side -- these will notably help with queries that join multiple tables together, a common scenario for the TPC-H benchmark.
- mason55 13y agoAwesome, can't wait to see more benchmarks. I would love to be able to switch back to 100% Postgres. IB gives us tons of speed but even ignoring the MySQL warts it just feels incomplete. And we ran into a bug in production where the order of AND was actually having an effect on query results, something that's completely unacceptable and makes me worry about my data.