Remove pgrust: the entry is cheating
Developers on the ClickHouse/ClickBench project have removed the 'pgrust' entry from their benchmark suite, citing cheating. The entry was found to be using hard-coded query results and cached data, violating the integrity rules of the performance test.
Why it matters
Maintaining the integrity of open-source benchmarks is essential for developers to accurately compare database performance and make informed infrastructure decisions.
Code Issues 24 ( 24 ) Pull requests 27 ( 27 ) Actions Security and quality Insights More items Remove pgrust: the entry is cheating (per-query kernels and result caching) - # 2165 # 2165 Merged alexey-milovidov merged 1 commit into main ClickHouse/ClickBench:main from remove-pgrust-cheating ClickHouse/ClickBench:remove-pgrust-cheating Copy head branch name to clipboard Sep 22, 2026 Conversation Commits 1 ( 1 ) Checks Files changed Merged Remove pgrust: the entry is cheating (per-query kernels and result caching) # 2165 alexey-milovidov merged 1 commit into main ClickHouse/ClickBench:main from remove-pgrust-cheating ClickHouse/ClickBench:remove-pgrust-cheating Copy head branch name to clipboard Conversation alexey-milovidov commented Sep 22, 2026 Copy link Copy Markdown Member This removes the pgrust entry (added in #1163 , updated to v0.4-preview in #2106 ) from the benchmark. The results it reports are produced by machinery written specifically for the 43 ClickBench queries, and its hot runs replay cached answers of the previous run.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in