#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 MarkusH):
* status: new => assigned
* owner: nobody => MarkusH
Comment:
I have an experimental / play PR that groups consecutive migrations that
need to be applied and only stores the state for the first of each of
them. This should drastically reduce the amount of used memory.
https://github.com/django/django/pull/4653
--
Ticket URL: <https://code.djangoproject.com/ticket/24743#comment:9>
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.3af3ff23b50fee8a06af7e7673651698%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
