Dieter Maurer wrote:
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the cache.
I therefore propose
sorry about the digest subject in the last email...
Message: 4
Date: Thu, 2 Jun 2005 19:28:34 +0200
From: Dieter Maurer [EMAIL PROTECTED]
Subject: [ZODB-Dev] [Proposal] Size controlled ZODB cache
To: zodb-dev@zope.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
[Chris Withers]
I don't suppose there's any way that, as part of this work, the size of
the cache could also be limited DURING a transaction? ...
That didn't look like part of Dieter's proposal to me wink.
It carries its own risks, and I'd rather not tie them together. For
example, _v_
Am Donnerstag, den 02.06.2005, 19:28 +0200 schrieb Dieter Maurer:
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the cache.
I therefore propose the implementation of
Dieter Maurer wrote:
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the cache.
I therefore
Shane Hathaway wrote:
Dieter Maurer wrote:
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the
