#27066: Possible Memory leak while evaluating a QuerySet
-------------------------------------+-------------------------------------
Reporter: RamezIssac | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset evaluation | Triage Stage:
memory leak | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by RamezIssac):
Thank you dear time for your quick reply,
What i'm referring to here is when i made the mistake of using
`bool(queryset)` , the server memory jumped and '''never''' returned back
to normal even after the function exit.
Something is not right here.
The only way to bring the memory back to normal was by restarting the
uwsgi process running the django instance.
It's not about that the line `bool(queryset)` takes longer time to
execute, or is heavy on memory;
But this line have a ''long lasting side effect'' on server memory
consumption.
--
Ticket URL: <https://code.djangoproject.com/ticket/27066#comment:2>
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/068.aeeec4164debbd1495ee50998da181d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
