-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[optimize](Transaction) Reduce the memory usage of transactions #57084
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
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-DS: Total hot run time: 190963 ms |
ClickBench: Total hot run time: 32.61 s |
|
run buildall |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
ClickBench: Total hot run time: 32.63 s |
|
run buildall |
ClickBench: Total hot run time: 28.6 s |
FE UT Coverage ReportIncrement line coverage |
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #27128
Problem Summary:
For a transaction with a status of visible, we only need to retain its label and successful status for EOS deduplication. Therefore, we have further cleared some unnecessary fields in the original code
pruneAfterVisibleto reduce the memory usage of completed transactions.According to the dump data analysis from JProfiler, the memory usage of transactions has been reduced to approximately one-tenth of the original.
(Be Careful) after this pr, some
SHOWsql will not show any msg for a visible transaction , but error. e.g.(TODO) In the future, we will impose certain limits on the number of transaction records for each table.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)