On Wednesday, March 30, 2011 06:48:15 pm dlamotte wrote: > I've documented what is going on here: > > http://stackoverflow.com/questions/5494178/why-doesnt-memory-get-released-t > o-system-after-large-queries-or-series-of-queri > > Basically, the memory doesn't "grow continuously" but it isn't > released to the system (yes DEBUG = False in settings.py). What I'm > seeing is that after executing a series of large querysets, the memory > never gets released to the system. I go into it in depth on the > stackoverflow question. Is this the behavior to be expected or am I > encountering a bug in Django? > > - Dan
Interestingly enough there was something like this today on stackoverflow[1] It's linux specific and uses sysctl. It might be helpful echo 1 > /proc/sys/vm/drop_caches [1] http://stackoverflow.com/questions/5483096/free-the-linux-page- cache/5483237#5483237 Mike -- Life is like an egg stain on your chin -- you can lick it, but it still won't go away. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
