Repository navigation
Fix slow repository dashboard with grouped counts - #16
Merged
Merged
Conversation
Merged
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
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.
Summary
The repository dashboard exceeds the proxy's 30-second timeout because its counts repeatedly scan the resources table for each repository. Calculate harvested counts once per repository and all resource counts in one grouped query, shared by the dashboard and public repository summary endpoint.
Deduplicate tags per resource to preserve the previous array-membership behavior. Keep publication-state precedence, suppressed counts, empty repositories, and latest harvest details unchanged. No database migration or new index is required.
Validation
git diff --checkpassed.The production benchmark measures database query execution, not end-to-end HTTP latency. This change has not been deployed.