#24745: Django 1.8+ Migrations Hold Onto Way More Memory
--------------------------------------+------------------------------------
Reporter: jpulec | Owner: nobody
Type: Cleanup/optimization | Status: new
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
--------------------------------------+------------------------------------
Comment (by jpulec):
For reference, I finally managed to run my tests against master. They
pass, but I think the margin is pretty slim. The VM I do all my testing in
has 2GB of RAM. On 1.8 and 1.8.1 my running test holds onto ~47% of my ram
according to top. On master that number comes down closer to 37% so it
runs for my use case.
However, it still shows that running all those migrations on creation of a
test database gobbles up all that ram and doesn't seem to release it right
away.
--
Ticket URL: <https://code.djangoproject.com/ticket/24745#comment:4>
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.3e6fb752a5531f08d785aae56c069502%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
