#24743: Django 1.8.1 migrations are actually slower than 1.8?
--------------------------------------+------------------------------------
     Reporter:  pzrq                  |                    Owner:  MarkusH
         Type:  Cleanup/optimization  |                   Status:  assigned
    Component:  Migrations            |                  Version:  1.8
     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
--------------------------------------+------------------------------------
Changes (by mjacksonw):

 * cc: mjacksonw (added)


Comment:

 We've been frustrated by this issue since 1.8 hit, seeing the same impacts
 as previous posters – the "Rendering model states" step taking several
 minutes when running fresh, which most notably impacts our testing
 environments.

 Our current "workaround," if you can call it that, is skipping migrations
 in testing except when testing our master branch, and squashing migrations
 as much as possible. Still, more than half of the time it takes to run our
 tests is consumed by this "Rendering model states" step.

 I tossed in MarkusH's PR (mentioned in comment:9) this morning, and ran
 `migrate` against a fresh database three times against stock 1.8.3, and
 three times with the changes from the PR:

 1.8.3 – Min: 4m56s, Max: 5m32s, Avg: 5m26s
 PR – Min: 32s, Max: 39s, Avg: 34s

 Specifically, the Rendering models states step went from about 4.5 mins to
 three or four seconds.

--
Ticket URL: <https://code.djangoproject.com/ticket/24743#comment:14>
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/062.6dc5c488ddfca446c3e9232729df454d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to