-
Notifications
You must be signed in to change notification settings - Fork 315
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
[proposal] cpu suppress policy should take fine-grined cpu orchestration into consideration #234
Comments
/assign jasonliu747 |
7 tasks
/area koordlet |
23 tasks
3 tasks
/assign @ZYecho |
ZYecho
added a commit
to ZYecho/koordinator
that referenced
this issue
Jul 19, 2022
Signed-off-by: Yue Zhang <huaihuan.zy@alibaba-inc.com>
jasonliu747
pushed a commit
to jasonliu747/koordinator
that referenced
this issue
Jul 26, 2022
…ator-sh#372) Signed-off-by: Yue Zhang <huaihuan.zy@alibaba-inc.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your proposal:
cpu suppress
policy change the cpuset of BE pod dynamically. fine-grined cpu orchestration rule should be considers. see #96 for more details.Why is this needed:
BE pod should not share CPU with LSE.
fairness of the BE cpuset should be considered, in case the BE cpuset are shared to only few LSR/LS pods.
Is there a suggested solution, if so, please add it:
take the cpu core number into account during the share of cpuset between BE and LSR/LS.
The text was updated successfully, but these errors were encountered: