3 ms·

Thanks! Totally. For us, the challenge lied in getting used to the async aspect of it, and architecting in such a way that queries that need to eliminate dupes

Thanks! Totally. For us, the challenge lied in getting used to the async aspect of it, and architecting in such a way that queries that need to eliminate dupes remain performant... Our initial approach was using ReplacingMergeTree but we couldn't get aggregation queries to run quickly enough... Any solution for that?

hodgesrm 3y ago
Yes, here's a blog that you might not have seen. Key factors in performance: partitioning so that ClickHouse does not need to run SELECT FINAL over a large number of parts and having a good ORDER BY. MergeTree queries are sensitive to ordering. https://altinity.com/blog/clickhouse-replacingmergetree-explained-the-good-the-bad-and-the-ugly https://altinity.com/blog/clickhouse-replacingmergetree-expl...