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.

Sign up for GitHub

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

Jump to bottom

Benchmark the dynamic watching implementation #598

Open
timflannagan opened this issue Nov 7, 2022 · 2 comments
Open

Benchmark the dynamic watching implementation #598

timflannagan opened this issue Nov 7, 2022 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
backlog

Comments

@timflannagan
Copy link
Contributor

Goal: bench the dynamic watching implementation in busier clusters to gather metrics that could be used to evaluate a long polling vs. dynamic watching implementation. The former is used in OpenShift environments, and the latter may be more expensive in production clusters that have many BundleDeployments being managed at a time.
@asmacdo
Copy link
Member

asmacdo commented Nov 10, 2022

@timflannagan suggests backlog/nice to have

@timflannagan timflannagan added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Nov 10, 2022
@timflannagan timflannagan added this to the backlog milestone Nov 10, 2022
@github-actions
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
2 participants
@asmacdo @timflannagan