Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.7] Bug 2073602: (Topology) Performance improvement by reducing rerenderings and deep-copy toJSON() calls #11309

Conversation

jerolimov
Copy link
Member

@jerolimov jerolimov commented Apr 8, 2022

Manual cherry-pick of 4.8 cherry-pick #11271.

There were just some issues with the imports.

Here is a recording of the import flows still works fine:

Peek.2022-04-11.09-24.mp4

Here is a recording comparing a production build 4.7 (left) against this PR (right), against a CRC:

Topology graph:

Peek.2022-04-11.09-32.mp4

Topology list:

Peek.2022-04-11.09-36.mp4

On a cluster, the difference is smaller... I will attach a cluster bot video as a comment.

by extracting k8s-ref methods similar to 4.9
and 'downgrade' newly added unit tests from
@testing-library/react to react-dom/test-utils
@openshift-ci openshift-ci bot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Apr 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 8, 2022

@jerolimov: This pull request references Bugzilla bug 2073602, which is invalid:

  • expected dependent Bugzilla bug 2066365 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.7] Bug 2073602: (Topology) Performance improvement by reducing rerenderings and deep-copy toJSON() calls

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 8, 2022
@openshift-ci openshift-ci bot added component/core Related to console core functionality component/shared Related to console-shared labels Apr 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 8, 2022

@jerolimov: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 11, 2022

@jerolimov: This pull request references Bugzilla bug 2073602, which is invalid:

  • expected dependent Bugzilla bug 2066365 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.7] Bug 2073602: (Topology) Performance improvement by reducing rerenderings and deep-copy toJSON() calls

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jerolimov
Copy link
Member Author

/label backport-risk-assessed
/cc @rottencandy @invincibleJai
/assign @christianvogt

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 11, 2022
@jerolimov
Copy link
Member Author

jerolimov commented Apr 11, 2022

On a 4.7 cluster bot instance with 100 Deployments:

4.7.mov

timecodes:
0:02 click on topology
0:18 the loading indicator disappears (after 16s)
0:42 first time the deployments are visible (without icons) (after 40s overall)
1:00 graph is movable, layout buttons don't work yet
1:28 fit to screen works the first time

@jerolimov
Copy link
Member Author

jerolimov commented Apr 11, 2022

On a cluster bot instance with this PR:

pr.mov

timecodes:
0:02 click on topology / the right namespace
0:05 the loading indicator disappears (after 3s)
0:07-0:08 first time the deployments are visible (without icons) (after 5-6s overall)
0:08 graph is movable, layout buttons don't work yet
0:42 fit to screen works the first time

/cc @jrichter1

@openshift-ci openshift-ci bot requested a review from jrichter1 April 11, 2022 08:36
@jerolimov
Copy link
Member Author

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 11, 2022

@jerolimov: This pull request references Bugzilla bug 2073602, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.z) matches configured target release for branch (4.7.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2066365 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2066365 targets the "4.8.z" release, which is one of the valid target releases: 4.8.0, 4.8.z
  • bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link
Contributor

@rottencandy rottencandy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on cluster.
GIt page does not crash, and topology does not lag for large number of deployments.
/lgtm

1.mp4

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 11, 2022
@jrichter1
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 11, 2022
@christianvogt
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 11, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, jerolimov, rottencandy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 11, 2022
@openshift-merge-robot openshift-merge-robot merged commit 6de52fc into openshift:release-4.7 Apr 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 11, 2022

@jerolimov: All pull requests linked via external trackers have merged:

Bugzilla bug 2073602 has been moved to the MODIFIED state.

In response to this:

[release-4.7] Bug 2073602: (Topology) Performance improvement by reducing rerenderings and deep-copy toJSON() calls

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. component/core Related to console core functionality component/shared Related to console-shared lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants