Optimize RankUsersByReviewLoad by using a graphql query - #13
Merged
Merged
Conversation
boolangery
force-pushed
the
feature/optimize-RankUsersByReviewLoad
branch
from
September 21, 2026 15:00
d6c0192 to
aa4afbd
Compare
boolangery
marked this pull request as ready for review
September 21, 2026 15:03
boolangery
force-pushed
the
feature/optimize-RankUsersByReviewLoad
branch
from
September 21, 2026 15:03
aa4afbd to
e65188a
Compare
boolangery
added this pull request to stack #15
September 21, 2026 15:13
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
2 participants
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.
Description
Reviewer notes
RankUsersByReviewLoad for 22 open PRs did 1 (ListPR) + 22×2 (s.PR get + ListAllReviewers, itself paginated ListReviews + ListReviewers) ≈ 60+ sequential REST calls.