misc(events-processor): Add new index to speed up in advance charge processing #3943
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
jdenquin
approved these changes
Jul 8, 2025
diegocharles
pushed a commit
that referenced
this pull request
Jul 11, 2025
…rocessing (#3943) ## Context A slow query was identified on the charge table: ``` SELECT count(*) FROM "charges" WHERE (plan_id = $1 AND billable_metric_id = $2) AND pay_in_advance = true AND "charges"."deleted_at" IS NULL ``` This query is made by the events processor to identify if an event needs to be billed in advance. The problem was identified because a big burst of event was post-processed, leading to a pike in CPU usage on the database. ## Description This PR only adds a new index to speed up the processing.
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.
Context
A slow query was identified on the charge table:
This query is made by the events processor to identify if an event needs to be billed in advance. The problem was identified because a big burst of event was post-processed, leading to a pike in CPU usage on the database.
Description
This PR only adds a new index to speed up the processing.