Drop unused database indexes - #664
Open
tdroxler wants to merge 1 commit into
Open
Conversation
Closed
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.
Remove all unused indexes from our prod database.
You can find the usage of all our indexes for our:
unused_indexes_report-fallback.txt
unused_indexes_report-replica.txt
unused_indexes_report.txt
main + replica have the same unused indexes, fallback differ a bit, which makes sense since fallback instance is used for a limited amount of endpoints.
I heavily tested it with the EB, everything is smooth, but I made this revert PR if anything goes terribly wrong.
Migration 12 drops 21 unused indexes, from the report, it can reclaim ~20 Go per DB instance and ~60 Go across main, replica, and fallback.
resolves #631