Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1810698

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: Evan Cordell <ecordell>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OLM QA Contact: Mike Fiedler <mifiedle>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: bandrade, dsover, ecordell, jiazha, lgallett, mifiedle
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1783284 Environment:
Last Closed: 2020-07-13 17:18:35 UTC Type: ---
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:    
Bug Blocks: 1783284    
Attachments:
Description Flags
olm-operator CPU none

Comment 4 Mike Fiedler 2020-03-10 23:51:33 UTC 
Verified on 4.5.0-0.nightly-2020-03-10-123441  olm-operator is basically steady at 20% of 1 core - it does drop off regularly but spends most of the time around 20%.   I'll attach a screenshot from grafana.
Comment 5 Mike Fiedler 2020-03-10 23:53:18 UTC 
Created attachment 1669134 [details]
olm-operator CPU
Comment 9 errata-xmlrpc 2020-07-13 17:18:35 UTC 
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:2409