fix: optimise pin content cid query #1573
Merged
Conversation
This file contains 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
adamalton
changed the title
|
Applying index in prod |
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.
Create an index on
pin(content_cid, status)to speed upuser_used_storagejoining and filtering.I'll create a separate issue to audit the use of
CREATE INDEX IF NOT EXISTS pin_status_idx ON pin (status);and to verify if it can be dropped in favor of this new one.Storage Limit Email Notifications Storage Limit Email Notifications #43 ran on staging in 11 minutes. ( staging amount of data is now comparable to prod).
🛑 The index has already been created in STAGING to test the performance against a large amount of data.