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

feat: Add rate limiting for computing kernel creation #2965

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

fregataa
Copy link
Member

@fregataa fregataa commented Oct 24, 2024

resolves #2952

Add rate limiting for computing kernel creation. The number of kernels that can be created within a single scheduler tick is now capped by a shared config value.
The value is saved in shared config(etcd) and the key of config value is config/session/max-num-kernel-to-create. The default value is null, which does not limit the number of kernels created in a single tick.

Checklist: (if applicable)

  • Milestone metadata specifying the target backport version
  • API server-client counterparts (e.g., manager API -> client SDK)

@fregataa fregataa added this to the 24.03 milestone Oct 24, 2024
@fregataa fregataa self-assigned this Oct 24, 2024
@github-actions github-actions bot added comp:manager Related to Manager component size:M 30~100 LoC labels Oct 24, 2024
@fregataa fregataa marked this pull request as ready for review October 24, 2024 08:42
@fregataa fregataa changed the title feat: limit max num of session to prepare in one tick feat: Add rate limiting for computing session creation Oct 24, 2024
@fregataa fregataa changed the title feat: Add rate limiting for computing session creation feat: Add rate limiting for computing kernel creation 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 size:M 30~100 LoC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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