-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[enhancement](load) avoid schema copy to reduce cpu usage #16034
Conversation
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.
clang-tidy made some suggestions
TeamCity pipeline, clickbench performance test result: |
clang-tidy review says "All clean, LGTM! 👍" |
clang-tidy review says "All clean, LGTM! 👍" |
@@ -242,7 +242,7 @@ Status TabletsChannel::_open_all_writers(const PTabletWriterOpenRequest& request | |||
wrequest.tuple_desc = _tuple_desc; | |||
wrequest.slots = index_slots; | |||
wrequest.is_high_priority = _is_high_priority; | |||
wrequest.ptable_schema_param = request.schema(); | |||
wrequest.table_schema_param = _schema; |
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.
_schema
is inited from request.schema()
, and it's life cycle is longer than delta writers, so we can use _schema
directly to avoid copying the schema twice(the first time is here, the second time is in the ctor of DeltaWriter)
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
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Proposed changes
Issue Number: close #xxx
Problem summary
some user reports that the cpu usage is quite high when data loading.
The flame graph shows that copy of the schema cost lots of cpu resources.
Checklist(Required)
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...