Bug 2006395
| Summary: | Developer Topology view slow and unresponsive with large number of workloads | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Andrew Collins <ancollin> |
| Component: | Dev Console | Assignee: | Christoph Jerolimov <cjerolim> |
| Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.8 | CC: | acancell, agawand, akanekar, akesarka, akundu, chiefjay2, cjerolim, cvogt, dhellard, eparis, hyoskim, jakumar, kjeeyar, mrobson, nmukherj, openshift-bugs-escalate, sdoyle, ssiddhar, steven.barre, tmicheli |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 4.12.0 | Flags: | jakumar:
needinfo-
jakumar: needinfo- jakumar: needinfo- jakumar: needinfo- jakumar: needinfo- |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
*Previously, there were unnecessary re-renderings and calculations when rendering the topology graph. As a result, the topology performance wasn’t good when showing hundreds of nodes. With this fix, there are several improvements on the topology page to enhance the performance. As a result, the topology can now handle many workloads and works better with hundreds of workloads. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2006395#[*BZ#2006395*])
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-19 10:17:45 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 Collins
2021-09-21 16:18:01 UTC
*** Bug 2008237 has been marked as a duplicate of this bug. *** We can confirm that the first wave of patches, which primary reduce the used memory are part of this releases: These fixes/improvements are part of the upcoming 4.10 GA * https://bugzilla.redhat.com/show_bug.cgi?id=1999796 * https://bugzilla.redhat.com/show_bug.cgi?id=2039315 * https://bugzilla.redhat.com/show_bug.cgi?id=2042829 This backports are available with 4.9.19 and newer * https://bugzilla.redhat.com/show_bug.cgi?id=2044287 * https://bugzilla.redhat.com/show_bug.cgi?id=2044292 * https://bugzilla.redhat.com/show_bug.cgi?id=2044259 This backports are available with 4.8.32 and newer * https://bugzilla.redhat.com/show_bug.cgi?id=2046051 * https://bugzilla.redhat.com/show_bug.cgi?id=2046215 * https://bugzilla.redhat.com/show_bug.cgi?id=2046043 (this was released in 4.8.31) As said, we continue our work to improve the performance even more. Can some of the customers can already confirm less/no browser crashs with this changes/releases? This changes increases the possible load in the topology, esp. if a namespace contains log of Secrets. We will also implement and backport two features for affected customers so that they can skip the topology on namespaces with a high load. For thiswe created two tickets: * https://bugzilla.redhat.com/show_bug.cgi?id=2060325 to allow the customers to configure another landing page then the topology. * https://bugzilla.redhat.com/show_bug.cgi?id=2060329 to show a warning if the number of workloads in the topology let us expect issues. We expect that we can deliver this within this month. I missed 4.7. The backports to 4.7 are merged and should be part of the next release. They are not available yet. Closing this based on comment https://bugzilla.redhat.com/show_bug.cgi?id=2006395#c34 ======================================================================================== from the engineering side, we worked on different fronts to close/handle this scenario. The issue is observed while rendering workloads in the topology view only if the number of workloads is more. Below are the individual tickets where we worked to improve the performance on load time but the topology view is graphical and CPU intensive it has improved to render but still it can't scale for a huge number of workloads. - https://bugzilla.redhat.com/show_bug.cgi?id=1999796 (Topology performance: Reduce the amount of data for Secrets), backported till 4.8 - https://bugzilla.redhat.com/show_bug.cgi?id=2042829 (Topology performance: HPA was fetched for each Deployment (Pod Ring)), backported till 4.8 - https://bugzilla.redhat.com/show_bug.cgi?id=2043064 (Topology performance: Unnecessary rerenderings in topology nodes (unchanged mobx props), in 4.10 Although the above helps in improving the performance to some extent like currently with 100 workloads no issues are observed but beyond 400 workloads can see lags/slowness. To handle this scenario we also introduced a check to notify the user while loading topology for more number of workloads(100) which will prevent the page from hanging, the details can be seen here - https://bugzilla.redhat.com/show_bug.cgi?id=2060329 (Detect the unsupported amount of workloads before rendering a lazy or crashing topology) backported till 4.9, 4.8 backport PR is already merged and is in process Can see the screenshots/gif here in the PR https://github.com/openshift/console/pull/11334 for it. Let us know in case of any issues cc @cjerolim The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |