Skip to content
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

koord-manager: support manually configured default cpu normalization settings #2128

Merged
merged 1 commit into from
Jul 15, 2024

Conversation

yangfeiyu20102011
Copy link
Contributor

@yangfeiyu20102011 yangfeiyu20102011 commented Jul 8, 2024

In some dedicated clusters, we don't need complex CPU models; instead, we prefer manually configured default CPU normalization settings for greater flexibility.

Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

V. Checklist

  • I have written necessary docs and comments
  • I have added necessary unit tests and integration tests
  • All checks passed in make test

Copy link

codecov bot commented Jul 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.68%. Comparing base (6861c87) to head (7fb6cc8).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2128   +/-   ##
=======================================
  Coverage   68.68%   68.68%           
=======================================
  Files         435      435           
  Lines       40703    40712    +9     
=======================================
+ Hits        27955    27965   +10     
  Misses      10337    10337           
+ Partials     2411     2410    -1     
Flag Coverage Δ
unittests 68.68% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@koordinator-bot koordinator-bot bot added size/S and removed size/M labels Jul 9, 2024
@yangfeiyu20102011 yangfeiyu20102011 changed the title koord-manager: support manually configured cpu normalization settings koord-manager: support manually configured default cpu normalization settings Jul 9, 2024
Copy link
Member

@saintube saintube left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@zwzhang0107
Copy link
Contributor

/lgtm
/approve

@yangfeiyu20102011
Copy link
Contributor Author

It still needs an approval. Thanks.
cc @saintube @FillZpp

@saintube
Copy link
Member

PTAL /cc @hormes

…settings

In some dedicated clusters, we don't need complex CPU models;
instead, we prefer manually configured default CPU normalization settings for greater flexibility.

Signed-off-by: yangfeiyu20102011 <yangfeiyu20102011@163.com>
Copy link
Member

@saintube saintube left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@koordinator-bot koordinator-bot bot added the lgtm label Jul 15, 2024
@hormes
Copy link
Member

hormes commented Jul 15, 2024

/approve

@koordinator-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hormes, saintube, zwzhang0107

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@koordinator-bot koordinator-bot bot merged commit 8cf0918 into koordinator-sh:main Jul 15, 2024
22 checks passed
zwForrest pushed a commit to zwForrest/koordinator that referenced this pull request Jul 16, 2024
…settings (koordinator-sh#2128)

Signed-off-by: yangfeiyu20102011 <yangfeiyu20102011@163.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants