#24745: Django 1.8+ Migrations Hold Onto Way More Memory
----------------------------+--------------------
Reporter: jpulec | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
After bumping to 1.8, rendering model states when running migrate seems to
consume a lot more memory. Somewhere on the order of 4x-6x more. It
doesn't look like this memory is properly released back to the OS after
running migrate, and just hangs around.
I discovered this calling manage.py test when using a custom test runner
that makes a subprocess call, and was unable to do so, because the python
process was already consuming so much memory that os.fork() couldn't
create a new process.
--
Ticket URL: <https://code.djangoproject.com/ticket/24745>
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/049.35ef038113050ea0f725da764c519696%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
