#22608: migrations slow (due to double working?)
-------------------------------------+-------------------------------------
Reporter: davids | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version:
Component: Migrations | 1.7-beta-2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by claudep):
In my profiling, I found that the most costly is rendering of the whole
project state, at least two times for each migration, once for
`MigrationExecutor.detect_soft_applied` and one or two times in
`Operation.database_forwards` (27.5 secs cum time for 17 calls in Django's
test suite, 8 migrations).
Andrew, it would be interesting to know if you tried to optimize this, and
particularly if `ProjectState.apps` could be reused/mutated or if this is
a lost battle.
--
Ticket URL: <https://code.djangoproject.com/ticket/22608#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.befa16e3a828b2692ee341818ee6c604%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
