feat: migrations should noop faster#103795
Merged
Conversation
wedamija
approved these changes
Nov 21, 2025
Member
wedamija
left a comment
There was a problem hiding this comment.
I tested this out locally and it seems pretty solid, nice improvement
IanWoodard
approved these changes
Nov 22, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
currently migrations noop takes ~10 minutes in us and a few minutes each in other regions and customers
i'd like to optimize the noop case by only checking the migrations table before dj_call_command migrate does all the heavy stuff like loading apps and models
getsentry upgrade --verbosity=2 --no-repair --noinputlocal noop before and after (3 databases - default, secondary, billing):