Optimize event processing to avoid N+1 queries - #364
Closed
cursor[bot] wants to merge 1 commit into
Closed
Conversation
Co-authored-by: jenn.muengtaweepongsa <jenn.muengtaweepongsa@sentry.io>
Author
|
Cursor Agent can help with this pull request. Just |
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #364 +/- ##
============================================
- Coverage 26.20% 26.04% -0.16%
- Complexity 323 324 +1
============================================
Files 77 77
Lines 3247 3240 -7
============================================
- Hits 851 844 -7
Misses 2396 2396 ☔ View full report in Codecov by Sentry. |
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.
Adds per-request caching for user potato statistics to eliminate redundant SUM queries.
The
potatoSentTodayandpotatoLeftTodaymethods were executing identical database queries multiple times within a single request. This change introduces a lightweight cache on theUserentity, ensuring these methods only query the daily potato count once per request andpotatoLeftTodayderives its value from the cachedpotatoSentTodayresult.