I dropped further development on it
once I evaluated the cost of having session data disappear (or become
inaccessible) when new memcache servers were added, or old ones removed.
Thanks for clearing that.
If you are *sharing* mutable session data between multiple long-running
requests, and
If you believe that 'faster' is raising conflicts due its own internal
data structures (OOBTree bucket splits), rather than in the
application-dveined session data, there is a conflict-free alternative
available: we found that it was slower than the other, and therefore
didn't scale as
Summary of messages to the zope-tests list.
Period Wed Apr 11 12:00:00 2007 UTC to Thu Apr 12 12:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Wed Apr 11 20:50:22 EDT 2007
Hi,
I am running a set of unit tests for a custom product nightly via a
buildbot installation, via bin/zopectl test -s Products.MyProduct in
zope 2.9.
Sorry in advance that this looks complicated - my query is actually
pretty straightforward!
Recently, I introduced a bug in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Apr 2007, at 13:35, Miles wrote:
However, having logged this, the testrunner proceeded to run all my
tests correctly, and so the buildbot reported a pass. I expected
the testrunner to bomb out on encountering this error, but it
didn't -
You could keep experimenting with values to reduce the chances of
conflicts. Perhaps sessions that last for days. With resolution of
hours. Disabling inband housekeeping.
Note that a session-timeout-minutes of 0 enables a slightly different
approach which has a little less active structure.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maciej Wisniowski wrote:
If you believe that 'faster' is raising conflicts due its own internal
data structures (OOBTree bucket splits), rather than in the
application-dveined session data, there is a conflict-free alternative
available: we found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
On 12 Apr 2007, at 13:35, Miles wrote:
However, having logged this, the testrunner proceeded to run all my
tests correctly, and so the buildbot reported a pass. I expected
the testrunner to bomb out on encountering
Maciej Wisniowski wrote at 2007-4-11 20:28 +0200:
Currently I have some problems with our application (Zope2.8.4)
and with Conflict Errors in sessions.
In general if we have few concurrent requests that are running
sometimes for 3-4 minutes (and they're touching session inside)
I get a lot of
Did you configure the faster SDC to disable the 'lazy' flag? That flag
disables modification of the SDC's linked list until the sesion is
actually modified, rather than being just accessed as you are doing here.
I tried both, with and without 'lazy' setting.
I used _BUCKET_TYPE =
10 matches
Mail list logo
