Bug 1909229

Summary: ci/prow/analyze - JavaScript heap out of memory (reduce cost)
Product: OpenShift Container Platform Reporter: Andrew Ballantyne <aballant>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, jhadvig, jokerman, pweil
Target Milestone: ---Keywords: UpcomingSprint
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-04 13:42:21 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:

Description Andrew Ballantyne 2020-12-18 16:55:58 UTC 
Description of problem:
In the growing fashion of dependencies, our CI for analyzing the code is taking more and more memory to run. It has gotten to the point over the last month that we have increased our memory from 10 gigs to 14 gigs to run the CI. We should look at why this is happening and if there are any avenues to reduce it.

As of writing this BZ, our status on the CI ci/prow/anyalze is:
Success rate over time: 3h: 25%, 12h: 35%, 48h: 49%

Version-Release number of selected component (if applicable):
4.7+ OpenShift Console

How reproducible:
Intermittent, once increased it gives us some breathing room, but seems to come back to this problem again.

Steps to Reproduce:
Run the CI locally and find some way to analyze it


Actual results:
Today it needs over 12gigs to run, we will likely have this problem in a few months when it hits the need of 14gigs to run.

Expected results:
Not to keep increasing the memory as a solution to this problem.

Additional info:

The two PRs that have increased it in the last 30days:
- Mine https://github.com/openshift/release/pull/14453
- Sam's https://github.com/openshift/release/pull/13798
Comment 3 Samuel Padgett 2021-01-04 13:42:21 UTC 
Looks like Ido has a fix ready under bug 1912115!

*** This bug has been marked as a duplicate of bug 1912115 ***