-
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
[opt](rowcount) refresh external table's rowcount async #32997
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 37447 ms
|
TPC-DS: Total hot run time: 183183 ms
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
9f8840a
to
b5cded1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
b5cded1
to
5a3a996
Compare
run buildall |
TPC-H: Total hot run time: 38668 ms
|
TPC-DS: Total hot run time: 180923 ms
|
ClickBench: Total hot run time: 30.12 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
5a3a996
to
17fa9f4
Compare
run buildall |
TPC-H: Total hot run time: 38258 ms
|
TPC-DS: Total hot run time: 183530 ms
|
ClickBench: Total hot run time: 29.43 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
PR approved by anyone and no changes requested. |
PR approved by at least one committer and no changes requested. |
In previous implementation, the row count cache will be expired after 10min(by default), and after expiration, the next row count request will miss the cache, causing unstable query plan. In this PR, the cache will be refreshed after Config.external_cache_expire_time_minutes_after_access, so that the cache entry will remain fresh.
In previous implementation, the row count cache will be expired after 10min(by default), and after expiration, the next row count request will miss the cache, causing unstable query plan. In this PR, the cache will be refreshed after Config.external_cache_expire_time_minutes_after_access, so that the cache entry will remain fresh.
Proposed changes
In previous implementation, the row count cache will be expired after 10min(by default),
and after expiration, the next row count request will miss the cache, causing unstable query plan.
In this PR, the cache will be refreshed after
Config.external_cache_expire_time_minutes_after_access
,so that the cache entry will remain fresh.
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...