Bug 1783284
| Summary: | OLM process CPU grows as number of projects increase. Spikes to 2+ cores every 5 minutes with 2K projects | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> | ||||||
| Component: | OLM | Assignee: | Evan Cordell <ecordell> | ||||||
| OLM sub component: | OLM | QA Contact: | Mike Fiedler <mifiedle> | ||||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||||
| Severity: | high | ||||||||
| Priority: | unspecified | CC: | dsover, ecordell, jiazha, nhale | ||||||
| Version: | 4.3.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.4.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1810698 (view as bug list) | Environment: | |||||||
| Last Closed: | 2020-05-13 21:55:15 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1810698 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1644870 [details]
OLM cpu on idle cluster with 2K projects
Verified on 4.4.0-0.nightly-2020-03-12-082023 Same results as for https://bugzilla.redhat.com/show_bug.cgi?id=1810698 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |
Created attachment 1644869 [details] OLM cpu on idle cluster after fresh install Description of problem: In a newly installed cluster, the olm process spikes to 15% of 1 core every 5 minutes at steady state - no activity. As the number of projects grows (project spec below), the 5 minute olm process spikes grow. At 2000 projects the spikes use 2 full cores every 5 minutes at steady state. Other control plane processes on the master do not exhibit this behavior when the cluster is idle. Each project: 6 builds 10 image streams 2 deployments 40 secrets 5 routes 20 configmaps Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-12-12-021332 How reproducible: always Steps to Reproduce: 1. Install a 4.3 cluster with 3 masters and 3 computes 2. Measure olm process CPU usage over time, observe spikes every 5 minutes to ~15% 3. Create more projects with the spec above 4. Observe the growth in the olm process usage CPU usage graphs for OLM process attached.