-
Notifications
You must be signed in to change notification settings - Fork 527
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
feat: supports changing number of executing cpu cores for manager api #1569
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.
Pretty good.Thank you for your contribution.
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.
CI failed. please use go fmt
to format the code.
Co-authored-by: nic-chen <33000667+nic-chen@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## master #1569 +/- ##
==========================================
+ Coverage 69.15% 73.21% +4.05%
==========================================
Files 49 86 +37
Lines 3164 2322 -842
Branches 0 584 +584
==========================================
- Hits 2188 1700 -488
+ Misses 728 622 -106
+ Partials 248 0 -248
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
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
@bisakhmondal merged, thanks a lot. |
You're welcome. Thanks for the review guys. |
Please answer these questions before submitting a pull request
Why submit this pull request?
Bugfix
New feature provided
Improve performance
Backport patches
Related issues
resolves feature: support custom CPU quantity used for
manager api
#682New feature or improvement
Supports changing the number of os threads attached to the goroutines.
For performance reason, if in the configuration file, the defined
max_cpu
is greater than the number of available cpu cores (including hyperthreading), themanager api
will stick to the max available cores. As it has a certain limit to boost the performance since the context switching of goroutines from the same os thread is a lot faster than goroutines from different threads.