Skip to content

Revert "Query condition cache: introduce selectivity threshold"#85965

Merged
rschu1ze merged 1 commit intoClickHouse:masterfrom
rschu1ze:revert-qcc-improvements
Aug 21, 2025
Merged

Revert "Query condition cache: introduce selectivity threshold"#85965
rschu1ze merged 1 commit intoClickHouse:masterfrom
rschu1ze:revert-qcc-improvements

Conversation

@rschu1ze
Copy link
Copy Markdown
Member

@rschu1ze rschu1ze commented Aug 21, 2025

Reverts #85253

Resolves https://github.com/ClickHouse/clickhouse-private/issues/36635

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh bot commented Aug 21, 2025

Workflow [PR], commit [827bd37]

Summary:

job_name test_name status info comment
Stateless tests (amd_binary, old analyzer, s3 storage, DatabaseReplicated, parallel) failure
03364_estimate_compression_ratio FAIL
03573_json_keys_with_dots FAIL
03595_alter_drop_column_comment_if_exists FAIL
Stress test (amd_ubsan) failure
Server died FAIL
Hung check failed, possible deadlock found (see hung_check.log) FAIL
Killed by signal (in clickhouse-server.log) FAIL
Fatal message in clickhouse-server.log (see fatal_messages.txt) FAIL
Killed by signal (output files) FAIL
Found signal in gdb.log FAIL

@rschu1ze rschu1ze force-pushed the revert-qcc-improvements branch 3 times, most recently from 7a7cf5e to 40d8642 Compare August 21, 2025 09:30
@rschu1ze rschu1ze marked this pull request as ready for review August 21, 2025 10:36
This reverts commit 1f2ae82.
@rschu1ze rschu1ze force-pushed the revert-qcc-improvements branch from a99d3a2 to 827bd37 Compare August 21, 2025 14:02
@clickhouse-gh clickhouse-gh bot added the pr-performance Pull request with some performance improvements label Aug 21, 2025
@rschu1ze
Copy link
Copy Markdown
Member Author

rschu1ze commented Aug 21, 2025

@zhongyuankai I unfortunately had to revert this PR.

The reason is that it caused a regression with at least two queries in ClickBench. The problem can be easily reproduced:

I can only imagine that this is related to more expensive locking, i.e. this optimization got lost by #85253.

If you have some time and like to help, it would be great if you could profile a bit and check what slows things down. Thanks!

@rschu1ze
Copy link
Copy Markdown
Member Author

Stateless tests (amd_binary, old analyzer, s3 storage, DatabaseReplicated, parallel)

Stress test (amd_ubsan)

@rschu1ze rschu1ze added this pull request to the merge queue Aug 21, 2025
Merged via the queue into ClickHouse:master with commit ece6fe4 Aug 21, 2025
120 of 122 checks passed
@rschu1ze rschu1ze deleted the revert-qcc-improvements branch August 21, 2025 19:15
@robot-clickhouse robot-clickhouse added the pr-synced-to-cloud The PR is synced to the cloud repo label Aug 21, 2025
@zhongyuankai
Copy link
Copy Markdown
Contributor

If you have some time and like to help, it would be great if you could profile a bit and check what slows things down. Thanks!

OK, I'll solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-performance Pull request with some performance improvements pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants