It turns out that the requests with high ram requirements are so well
distributed
that I'm not running out of memory. So my initial concerns (the first mail
in this
thread) can be forgotten. YAY.
-Andrin
On Wed, Feb 22, 2012 at 9:08 AM, Robert Kluin wrote:
> Hey Alex,
> I should probably have
Hey Alex,
I should probably have stated this better as memory is not always
handled well. For example, the ext.db code keeps many copies of the
data in various forms. This can cause rapid and unexpected memory
blowups, and the result is something that appears similar to a memory
leak. As Brian
Hi Mike,
On Wed, Feb 22, 2012 at 7:22 AM, Mike Wesner wrote:
> I would love to learn more from google on python memory handling. As
> Robert mentioned, we have observed that memory is not released/garbage
> collected on python 2.5 instances. It seems to just hold on to it.
> This works because
I know that, but I thought it might still be relavant.
On Feb 21, 3:13 pm, alex wrote:
> The whole point of this topic was python27 runtime, multithreading and
> concurrent requests. Your specific case, plus python 2.5, doesn't
> necessarily means memory leaks in the runtime itself. I'd profile m
The whole point of this topic was python27 runtime, multithreading and
concurrent requests. Your specific case, plus python 2.5, doesn't
necessarily means memory leaks in the runtime itself. I'd profile my code
that handles most frequently accessed URLs to start off.
--
You received this messa
I would love to learn more from google on python memory handling. As
Robert mentioned, we have observed that memory is not released/garbage
collected on python 2.5 instances. It seems to just hold on to it.
This works because the instances don't live forever and eventually get
shutdown and new o
