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

Test using Active queue "Activate Siblings" vs Current approach #73

Closed
vsoch opened this issue Apr 9, 2024 · 1 comment
Closed

Test using Active queue "Activate Siblings" vs Current approach #73

vsoch opened this issue Apr 9, 2024 · 1 comment

Comments

@vsoch
Copy link
Member

vsoch commented Apr 9, 2024

Coscheduling uses a strategy of moving siblings to the active Q when a pod that is about to hit a node hits the Permit endpoint. The strategy I have in place to schedule the first pod seems to be working OK, but I'd like to (after we merge the current PR) test this approach. I can see pros and cons to both ways - having to rely on another queue (subject to other issues) seems less ideal than having them all scheduled at the right time. On the other hand, if something might happen with the latter approach that warrants the active queue, maybe it makes sense. I think empirical testing can help us determine which strategy we like best (or even a combination of the two).

@vsoch
Copy link
Member Author

vsoch commented May 22, 2024

This will be closed with #69

@vsoch vsoch closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant