Optimize network list loading performance by using stored authorization status#647
Merged
Optimize network list loading performance by using stored authorization status#647
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a performance issue caused by making individual API calls to zt controller for each member of each network when loading the network list. For instances with many networks and members, this resulted in hundreds of sequential API calls, significantly increasing network page load time.
This PR will add authorized status to database instead of making API calls.
Note: After updating, users will need to open each network individually to update the authorized status in the database. Until this is done, the "Nodes Act/Tot" column on the network page may display inaccurate information during initial load.
Resolves #638