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

Limit the number of sessions (and their kernels) created at a single scheduler tick #2952

Open
fregataa opened this issue Oct 23, 2024 · 0 comments · May be fixed by #2965
Open

Limit the number of sessions (and their kernels) created at a single scheduler tick #2952

fregataa opened this issue Oct 23, 2024 · 0 comments · May be fixed by #2965
Assignees
Labels
comp:manager Related to Manager component
Milestone

Comments

@fregataa
Copy link
Member

fregataa commented Oct 23, 2024

When there are a large number of scheduled sessions for a single scheduler tick, making all RPC calls at once may cause the manager performance issues and potential hangs.

Let's apply the concept of more_itertools.chunked() when making the RPC calls for each kernel creation, introducing a new configuration option to specify the chunk size.

We should also check if the hang happens when there are overlapping RPC calls to the same agent, even when there is a low number of kernels to create.

@fregataa fregataa self-assigned this Oct 23, 2024
@fregataa fregataa linked a pull request Oct 24, 2024 that will close this issue
2 tasks
@achimnol achimnol added the comp:manager Related to Manager component label Oct 24, 2024
@achimnol achimnol modified the milestones: 24.09, 24.03 Oct 24, 2024
@achimnol achimnol changed the title Add config (or const) to limit the number of session created by a scheduler in one tick Limit the number of sessions (and their kernels) created at a single scheduler tick Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp:manager Related to Manager component
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants