address performance issues w/passrate #63
+48
−126
Conversation
This file contains 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
|
new UI view doesn't look that much different, but its markedly more performant. idk if it will be a big enough performance boost tho |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
when running in an environment where target entries scale and become very large, the pass rate functionality can cause the targets and tests views to become slow and unresponsive. to address this issue, i'm removing pagination and pass rate from these views and adjusting the backend queries respectively to see if this improves performance enough to make the application more responsive. I'm also adjusting the cache policy from cache and network to the default and adding a long poll interval and indexing the label fields of target pair and test collection in the db