Dieter Maurer wrote:
This is standard behaviour with long running processes on
a system without memory compaction:
Of course, I remember now, there was something about that in my
Operating Systems course ten years ago :-) I suppose the bigger page
sizes used on some architectures doesn't
Izak Burger-2 wrote:
Dieter Maurer wrote:
This is standard behaviour with long running processes on
a system without memory compaction:
Of course, I remember now, there was something about that in my
Operating Systems course ten years ago :-) I suppose the bigger page
sizes used on
Hi all,
I'm sure this question has been asked before, but it drives me nuts so I
figured I'll ask again. This is a problem that has been bugging me for
ages. Why does zope memory use never decrease? Okay, I've seen it
decrease maybe by a couple megabyte, but never by much. It seems the
There was a recent modification to limit the ZODB cache to a set size. i.e.
Limit the size of memory usage to 128MB.
The original feature was implemented here:
http://svn.zope.org/ZODB/branches/dm-memory_size_limited-cache/
You can get the feature+3.8 branch of the ZODB from:
Hi Alan
Thanks for the notice. We'll give this a go and report back.
Do you know how exactly it is decided what stays in the cache?
--
Roché Compaan
Upfront Systems http://www.upfrontsystems.co.za
On Wed, 2008-09-17 at 10:26 -0500, Alan Runyan wrote:
There was a recent
Izak Burger wrote at 2008-9-17 12:10 +0200:
I'm sure this question has been asked before, but it drives me nuts so I
figured I'll ask again. This is a problem that has been bugging me for
ages. Why does zope memory use never decrease? Okay, I've seen it
decrease maybe by a couple megabyte, but
Alan,
I'm replying to the Zope list also, because this issue is perhaps
related to other components there.
I'm running into the same situation: The python process running my Plone
site is steadyly growing.
I'm using Zope2.9.8-final (the one which works with Plone 2.5.5).
What is the plan for
