Optimize count query in MarketingActivityRepository#5
Open
d3f3kt wants to merge 1 commit intooroinc:masterfrom
Open
Optimize count query in MarketingActivityRepository#5d3f3kt wants to merge 1 commit intooroinc:masterfrom
d3f3kt wants to merge 1 commit intooroinc:masterfrom
Conversation
…mization. For example if the the marketing activity list contains a lot of items (~1M) but only a ~10 different campaigns, postgres will ignore the index generation for campaign_id. This leads to query time above 30 seconds. This fix will not count the items but will query for the first marketing activity item for the given campaign.
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.
In some cases the count query can take a lot of time and need an optimization.
For example if the the marketing activity list contains a lot of items (~1M) but only a ~10 different campaigns, postgres will ignore the index generation for campaign_id. This leads to query time above 30 seconds.
This fix will not count the items but will query for the first marketing activity item for the given campaign.