Avoid triggering N+1 on index page#38
Merged
fractaledmind merged 1 commit intofractaledmind:mainfrom Apr 8, 2024
Merged
Conversation
fractaledmind
approved these changes
Apr 8, 2024
Owner
fractaledmind
left a comment
There was a problem hiding this comment.
Great catch. And great PR. Thank you
fractaledmind
added a commit
that referenced
this pull request
Apr 9, 2024
fractaledmind
added a commit
that referenced
this pull request
Apr 9, 2024
After PR #38, ensure that last_seen_at is a DateTime object
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.
I noticed a couple of N+1, namely:
recent_occurrenceis being computed but never usedoccurrences.sizeis not being computed, triggers N+1To test it, I created a couple of exceptions locally

Queries before:
after: