feat(search): reduce DB pressure during email search backfills#2007
Merged
feat(search): reduce DB pressure during email search backfills#2007
Conversation
gbirman
changed the title
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
EmailThreadBatchMessageSQS type that batches 50 threads per message (vs 1 thread per message previously)get_parsed_search_messages_by_thread_idsDB query usingWHERE thread_id = ANY($1)to fetch messages for all 50 threads in a single queryThis reduces DB round-trips by ~50x during backfills. Previously each thread required 4 DB queries (messages + senders + recipients + labels). Now 50 threads share those same 4 queries.