-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[draft] Collect bloom runtime filter filtering statistics. #47305
base: master
Are you sure you want to change the base?
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
TPC-H: Total hot run time: 32520 ms
|
TPC-DS: Total hot run time: 186963 ms
|
ClickBench: Total hot run time: 30.16 s
|
TeamCity be ut coverage result: |
What problem does this PR solve?
Runtime filters can be executed either as expressions or predicates.
When executed as predicates, some filters may be transformed into other predicates
(e.g., minmax filters become max/min predicates for index lookup, or combined with
other predicates into key ranges). In such cases, it's difficult to track the filter id.
Therefore, we only collect statistics for bloom filters here to help optimizer analysis.
like this
data from
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)