On Wed, 2008-11-19 at 11:53 +1100, Malcolm Tredinnick wrote:
[...]
> Once memory gets to the over-allocated stage,
> it will be reclaimed...
Thinking about it further, this is rubbish.
Details (if you care): Memory allocated with malloc(), etc, won't
necessarily be reclaimed, since it can only
On Tue, 2008-11-18 at 08:24 -0800, 7timesTom wrote:
[...]
> Maybe this post will help someone else also one thing I don't
> understand:
>
> Why wasn't the memory returned to me after each page view? Why was an
> apache off/on necessary to clear memory? And is there anything I can
> do to help
7timesTom wrote:
> cars = Car.objects.filter(...) #upto 2000 items
> msg =... len(cars) # can you see the massive memory use here?
This is actually well documented:
http://docs.djangoproject.com/en/dev/ref/models/querysets/#when-querysets-are-evaluated
Are you using MySQL? It's been implicated in these sorts of issues
before: http://nedbatchelder.com/blog/200809/a_server_memory_leak.html
--Ned.
http://nedbatchelder.com
7timesTom wrote:
> Some time ago Webfaction notified me "Memory usage over your
> limit" (80MB) It's taken me ages to find
Some time ago Webfaction notified me "Memory usage over your
limit" (80MB) It's taken me ages to find this darn memory leak! It was
one short line that didn't even add functionality to my users.
I have 2000 items (cars) in a database table, which my users can
search through. After the webfaction
5 matches
Mail list logo
