On 02/28/2011 07:37 PM, Shane Hathaway wrote:
On 02/28/2011 08:19 AM, Maurits van Rees wrote:
I wonder if there is some code that mistakenly throws away the wrong
blob; it should throw away the oldest one I'd think, and not the one
that it just loaded.
The workaround is probably just to not
Op 01-03-11 09:17, Shane Hathaway schreef:
On 02/28/2011 07:37 PM, Shane Hathaway wrote:
On 02/28/2011 08:19 AM, Maurits van Rees wrote:
I wonder if there is some code that mistakenly throws away the wrong
blob; it should throw away the oldest one I'd think, and not the one
that it just
On Mon, Feb 28, 2011 at 4:19 PM, Maurits van Rees
m.van.r...@zestsoftware.nl wrote:
This is with RelStorage 1.5.0-b1, with blob-dir enabled, shared-blob-dir
false and a low blob-cache-size, say 10 bytes. Using Plone 3.3.5,
plone.app.blob 1.3, plone.app.imaging 1.0.1, but the same is
On Mon, Feb 28, 2011 at 16:22, Hanno Schlichting ha...@hannosch.eu wrote:
Blobs are considered experimental in ZODB 3.8. Especially the entire
blob cache changed completely for ZODB 3.9.
I think you might want to upgrade to Plone 4 and ZODB 3.9 to get a
stable environment. Or you'll likely
Op 28-02-11 16:34, Martijn Pieters schreef:
On Mon, Feb 28, 2011 at 16:22, Hanno Schlichtingha...@hannosch.eu wrote:
Blobs are considered experimental in ZODB 3.8. Especially the entire
blob cache changed completely for ZODB 3.9.
I think you might want to upgrade to Plone 4 and ZODB 3.9 to
On Mon, Feb 28, 2011 at 5:09 PM, Maurits van Rees
m.van.r...@zestsoftware.nl wrote:
Op 28-02-11 16:34, Martijn Pieters schreef:
On Mon, Feb 28, 2011 at 16:22, Hanno Schlichtingha...@hannosch.eu wrote:
Blobs are considered experimental in ZODB 3.8. Especially the entire
blob cache changed
On Mon, Feb 28, 2011 at 17:09, Maurits van Rees
m.van.r...@zestsoftware.nl wrote:
That works: the blobs stay. But then it looks like the blob cache size
is only checked once when starting up the zope instance. For example
with a blob cache size of 100,000 bytes and two images of about 65K and
On 02/28/2011 08:19 AM, Maurits van Rees wrote:
I wonder if there is some code that mistakenly throws away the wrong
blob; it should throw away the oldest one I'd think, and not the one
that it just loaded.
The workaround is probably just to not set the blob-cache-size this low.
But I
