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-scheduler supports CPU exclusive policy #227

Closed
eahydra opened this issue Jun 8, 2022 · 0 comments
Closed

koord-scheduler supports CPU exclusive policy #227

eahydra opened this issue Jun 8, 2022 · 0 comments
Labels
Milestone

Comments

@eahydra
Copy link
Member

eahydra commented Jun 8, 2022

What is your proposal:

The scheduler can coordinate the arrangement between latency-sensitive applications. For example, the same latency-sensitive applications can be mutually exclusive in the CPU dimension, and latency-sensitive applications and general applications can be deployed in the CPU dimension affinity. Costs can be reduced and runtime quality can be guaranteed.

More details please refer to #96

Some latency-sensitive applications need to

Why is this needed:

Is there a suggested solution, if so, please add it:

@eahydra eahydra added this to the someday milestone Jun 8, 2022
@eahydra eahydra added enhancement New feature or request area/koord-scheduler labels Jun 8, 2022
@eahydra eahydra changed the title koord-scheduler supports CPU isolation strategy, such as Core level, NUMA Node level koord-scheduler supports CPU exclusive policy Jun 20, 2022
@eahydra eahydra modified the milestones: someday, v0.6 Jun 20, 2022
@eahydra eahydra closed this as completed Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant