Bug 1810698 - OLM process CPU grows as number of projects increase. Spikes to 2+ cores every 5 minutes with 2K projects
Summary: OLM process CPU grows as number of projects increase. Spikes to 2+ cores ev...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: Evan Cordell
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks: 1783284
TreeView+ depends on / blocked
 
Reported: 2020-03-05 18:17 UTC by Evan Cordell
Modified: 2020-07-13 17:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1783284
Environment:
Last Closed: 2020-07-13 17:18:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
olm-operator CPU (52.18 KB, image/png)
2020-03-10 23:53 UTC, Mike Fiedler 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github operator-framework operator-lifecycle-manager pull 1353 0 None closed Bug 1810698: feat(jitter): add jitter to controllers to smooth out our spiky resource 2020-06-29 06:38:30 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:18:54 UTC

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
Note You need to log in before you can comment on or make changes to this bug.