-
Notifications
You must be signed in to change notification settings - Fork 110
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(sysadvisor): export region reclaimable info as non-reclaim when dedicated_cores can not be co-located with reclaimed_cores #345
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #345 +/- ##
==========================================
+ Coverage 53.43% 53.55% +0.11%
==========================================
Files 434 436 +2
Lines 47563 47963 +400
==========================================
+ Hits 25415 25685 +270
- Misses 19295 19396 +101
- Partials 2853 2882 +29
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
94713d5
to
abcc858
Compare
abcc858
to
e2d8795
Compare
e2d8795
to
ef3b565
Compare
@@ -38,6 +42,7 @@ import ( | |||
|
|||
type QoSRegionDedicatedNumaExclusive struct { | |||
*QoSRegionBase | |||
podUID string |
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.
personally, I would prefer not to define podUID here, since it indicates that only contain one pod can be supported, but the podSet indicates that we should support multiple pods, and it may cause a lot of confusion as the logic goes more and more complex
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.
or we can redefine the high-level design, i.e. "whether it is reasonable to make every region to contain a podSet "
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.
It is necessary to keep the podset because we need to calculate resource usage by it. NewQoSRegionDedicatedNumaExclusive accept containerInfo as one of the parameters indicate that only this region only belong to single Pod.
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.
still confused for keeping both podSet and podUID; besides, NewQoSRegionDedicatedNumaExclusive accept containerInfo as one of the parameters
is not a solid reason for keeping podUID or indicating there should be only one pod in this region, since all regions accept containerInfo as one of the parameters (cause we need for its owner pool name) ...
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.
well, I removed podUID of QoSRegionDedicatedNumaExclusive and use getPodUID to get it.
…m when dedicated_cores can not be co-located with reclaimed_cores Signed-off-by: linzhecheng <linzhecheng@bytedance.com>
ef3b565
to
bdd0f20
Compare
What type of PR is this?
Enhancements
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer: