#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: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by MarkusH):
Replying to [comment:27 prophile]:
> For what it's worth, this patch greatly improved model state rendering
for us:
>
> {{{
> diff -r /tmp/saved-django/db/migrations/executor.py
contrib/django/db/migrations/executor.py
> 99,100d98
> < if 'apps' not in state.__dict__:
> < state.apps # Render all real_apps -- performance
critical
> }}}
Not really, it just delays the rendering.
The `Rendering model state` will be faster, yes. But instead of rendering
the models there, Django will render them when applying the migrations. At
that phase it might even look like migrations are stuck.
--
Ticket URL: <https://code.djangoproject.com/ticket/24743#comment:28>
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.668d1a48e0722f9f7d49d879366d130a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
