Amos Bird

Thanks for the feedback! I'd actually prefer to have this PR merged into the ClickBench repository for a few reasons: - A continuously updated tuned baseline: This fork plays a...

> Yes, it is entirely possible. Hmm, I was actually thinking of a different strategy: keep using the same type, but recognize the underlying streams — and if there's a...

> Maybe we can try. Although, having to look up an additional file looks hacky. Another solution is to approach it as different column representations, like ColumnSparse (how do we...

> As long as the results are reproducible, let's merge. I've just merged an [additional optimization](https://github.com/ClickHouse/ClickHouse/pull/82478) from my team that addresses the Q23 issue . With this fix, the results...

I've implemented the [separate size stream string format](https://github.com/ClickHouse/ClickHouse/pull/82850) with `.size` subcolumn support and corresponding optimizations. However, the performance improvement is only significant in Q27, while other queries show negligible gains...

@rschu1ze, thanks a lot! Just wondering — the entry appears on the leaderboard, but it only shows the name without rendering the actual benchmark results. Do you know what might...

It's because we added `tuned` field recently. Here is the fix https://github.com/ClickHouse/ClickBench/pull/421 . cc @rschu1ze

> Is there a plan to introduce a PR ... There is definitely a plan, but since I already have several PRs pending, it will take some time to prepare...

Sure. I'll rebase it today.

> The change looks good, however it is not clear why this only "helps" but not fixes the situation in the mentioned issue? The description was inaccurate. It's actually "fixes".