Bug 2053685

Summary: Topology performance: Immutable .toJSON consumes a lot of CPU time when rendering a large topology graph (~100 nodes)
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: Christoph Jerolimov <cjerolim>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: high    
Version: 4.6CC: aos-bugs, nmukherj, viraj
Target Milestone: ---   
Target Release: 4.11.0   
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: 2022-08-10 10:49:30 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:    
Bug Blocks: 2054757    

Description Christoph Jerolimov 2022-02-11 18:47:50 UTC 
Description of problem:
When analyzing some topology performance issues it shows that the Immutable method to convert immutable data structures to 'plain' JavaScript objects via toJSON() consumes a lot of time. The result is a slow starting topology and rerender process when showing more then 100 nodes.

Version-Release number of selected component (if applicable):
4.6+

How reproducible:
Always on a cluster with many many Deployments (tested with round about 100 nodes)

Steps to Reproduce:
1. Create many nodes, see https://github.com/jerolimov/openshift/tree/master/loadtest
2. Open the dev perspective, switch to the add page
3. Enable profiling tools in your browser
4. Open the topology and stop profiling after page is loaded

Actual results:
With around 100 nodes (Deployments for example) the topology is really slow and laggy. A lot of CPU time is consumed in ImmutableJS toJSON

Expected results:
A faster topology. :)

Additional info:
Comment 3 Christoph Jerolimov 2022-03-17 11:42:23 UTC 
Tested topology with 100 Deployments on 4.11.0-0.nightly-2022-03-16-103946 and it is quite fast.

It's less responsible then 4.10 because it makes to many API calls to /api/kubernetes/apis/authorization.k8s.io/v1/selfsubjectaccessreviews but we will address this in another issue.
Comment 5 errata-xmlrpc 2022-08-10 10:49:30 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069