Merged
Conversation
The homepage query scans all 508K submissions and sorts 189K rows for ranking, taking ~1.3s. Add a 30-second in-memory cache following the same pattern used in events.py to make repeated homepage loads near-instant.
msaroufim
added a commit
that referenced
this pull request
Feb 26, 2026
This reverts commit beebbf1.
msaroufim
added a commit
that referenced
this pull request
Feb 26, 2026
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.
Summary
/api/leaderboard-summariesevents.pyWhy
The homepage summary query takes ~1.3s because it scans all 508K submissions and sorts 189K rows across all 30 leaderboards to compute rankings. With the cache, only the first request in each 30s window hits the database — subsequent requests return instantly.
EXPLAIN ANALYZEon prod showed:Test plan
?v1_querystill works independently