Goal

In OLMv0, there were instances where performance degradations over time caused problems, especially with hyper shift, micro shift, and very large-scale clusters.

For OLMv1, we need to establish performance high water marks via benchmarks and then enforce those high water marks to prevent performance regressions.

Benefit Hypothesis:

What are the benefits (to Red Hat, eventually to customers, to the community, etc.)? Does it improve security, performance, supportability, etc? Why is work a priority?

We believe that the result of doing this work will be that OLMv1 feature additions will have known performance impacts and can be specifically measured to ensure they do not unnecessarily degrade cluster performance. This will ultimately result in cost savings for customers and our own managed cluster service.

Resources

Add any resources (docs, slides, etc.) pertinent to the definition of the work. These might not be known until later. Update as necessary.

Responsibilities

Indicate which roles and/or teams will be responsible for contributing to the initiative and generally what they might be expected to do.

OLM team will lead this effort, but may need to pull in other teams as necessary (TRT, DPTP, monitoring, etc.)

Success Criteria

Provide some examples of how we will know if we have achieved the goal. What can be measured to determine success? What observable actions/outcomes that can be seen to determine success? Specific, Measurable, Achievable, fits within the Time-box.

Downstream CI jobs capture OLMv1 performance metrics (TBD), compare them to an established baseline, and then pass/fail a PR based on whether they meet the required performance characteristics.

Results

Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.