Cache dashboard query #16165 #198
Merged
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
cigamit
added
enhancement
Contributor
There was a problem hiding this comment.
Pull request overview
This PR implements caching for the expensive dashboard jobs graph query to improve performance. The view is called excessively by the UI, and the underlying database query is resource-intensive. The solution memoizes the query results for 15 seconds based on unique user ID and query parameters (time period and job type).
Key changes:
- Refactored dashboard computation logic into a separate static method
_compute_dashboard_jobs_graph - Applied
@memoize(ttl=15)decorator to cache results for 15 seconds per unique parameter combination - Converted user object to user_id for proper caching key generation
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
TheWitness
approved these changes
Dec 9, 2025
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.
This causes an expensive query and the view sometimes called excessively by the UI. Memoize per unique user and params (time period) for 15s.