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

Deterministic assignment of sandbox IDs #1213

Open
gollux opened this issue Aug 9, 2022 · 0 comments
Open

Deterministic assignment of sandbox IDs #1213

gollux opened this issue Aug 9, 2022 · 0 comments

Comments

@gollux
Copy link
Contributor

gollux commented Aug 9, 2022

When using CMS with the Isolate sandbox, the assignment of sandbox IDs for various purposes (compilation, solution, manager for communication tasks, etc.) is somewhat haphazard and unpredictable. So even though Isolate itself supports pinning of sandboxes to specific CPU cores and/or NUMA nodes, it cannot be used in CMS for pinning a specific type of sandbox. This would be very useful to minimize time measurement noise in various types of interactive tasks.

I would like to make the assignment of IDs configurable. That is, to allow specifying a map from a (shard, purpose) pair to Isolate's sandbox ID. For the purposes, we can re-use existing sandbox names, only in case of communication tasks with multiple instances of the solution, the name would have to be extended to include instance number.

@wil93 wil93 added this to the P2 milestone Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants