Can GROUP BY still be optimized after all these years?
0 comments
- Points93
- Comments15
0 comments
Story details from Hacker News ↗ · linked article on pivotlake.io.
Can GROUP BY still be optimized after all these years? was first seen on Hacker News · Front page on Nov 7, 2026. Since then it has appeared in 67 checks on 1 different day. Its best position was #15 of 30, reached on Nov 7, 05:52 UTC. It dropped off the list after Nov 7, 16:39 UTC.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
I wonder why you didn't opt to perform a Top-K aggregation in each partition in parallel. That would give you both a reduction of elements in each partition and also the correct maximum of each partition, which can be used for further pruning.
Their clickbench results look really good. https://benchmark.clickhouse.com/#system=+liH|Hoaus|DcD|ucqs...
Neat! For others, the data structure they are describing is a count-min sketch. It looks like they're using it to set a bound on elements that can enter the group-by and using it to skip a bunch of extra work
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 7, 16:39 UTC, after 1 day of trending.
#15 on Hacker News · Front page, on Nov 7, 05:52 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 7, 2026 and has been on the list on 1 day (67 checks) since.
93 points and 15 comments; submitted by ntur1337 on Nov 3, 2026.