-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
executor: allocate handles on demand when build table tasks #57940
Conversation
Signed-off-by: zyguan <[email protected]>
Hi @zyguan. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #57940 +/- ##
================================================
+ Coverage 73.1461% 75.0716% +1.9254%
================================================
Files 1675 1720 +45
Lines 461870 471045 +9175
================================================
+ Hits 337840 353621 +15781
+ Misses 103283 95323 -7960
- Partials 20747 22101 +1354
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Good finding
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfzjywxk, crazycs520 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest |
@cfzjywxk: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/ok-to-test |
/retest |
/test fast_test_tiprow |
@zyguan: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@ti-chi-bot[bot]: The specified target(s) for
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/retest |
2 similar comments
/retest |
/retest |
What problem does this PR solve?
Issue Number: ref #56649
Problem Summary:
indexWorker.extractTaskHandles
will allocate a lot of memory even when there are a few handles.Let prepare sysbench oltp data with
--secondary
option and run oltp_point_select workload. The cpu and heap profiles are shown as the following. When callingextractTaskHandles
, it's always pre-allocate a large slice for task handles.What changed and how does it work?
Simply delay the slice allocation and use the first chunk size as the init capacity.
Here are the benchmark results:
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.