OK... more info... here's my setup.
1 ZEO server, 3 clients (client 1, client 2, client 3).
client 1 is on the same physical machine as the server.
client 2 is on a different machine, but close by
on a high-bandwidth network.
client 3 is on a third machine on the same network.
If I make chang
On Thu, Jul 31, 2003 at 12:13:40PM -0400, Shane Hathaway wrote:
> >This is clearly problematic. At what point is client 2 supposed to
> >see the new object??
>
> Immediately. You are experiencing a bug. ;-)
OK... is this a known bug? Is it a bug in ZEO or Zope or what?
--
Paul Winkler
http:/
On Thu, Jul 31, 2003 at 10:06:08AM -0400, Shane Hathaway wrote:
> Jim and PythonLabs put a bunch of work into optimizing ZEO cache
> validation earlier this year, and now it's quite speedy.
Which reminds me... Is it expected that ZEO can take quite a while
to show a new object on all clients?
W
Andrew Sydelko wrote:
It's faster especially compared to ZEO 1.x, but also compared to earlier
versions of ZEO 2.x/ZEO from ZODB3.1.x.
At one point, changes were made to the initial cache invalidation check
that caused ZEO startup time to become significantly faster.
Before this change the ZEO c
On Thu, 31 Jul 2003 8:49am, Shane Hathaway wrote:
Andrew Sydelko wrote:
I've seen no problems with imports. And if anything, the cache
implementation in the ZODB3.1.2 version of ZEO made a remarkable
performance difference.
... as compared with earlier versions or later versions? I hope it's
ge
Andrew Sydelko wrote:
I've seen no problems with imports. And if anything, the cache
implementation in the ZODB3.1.2 version of ZEO made a remarkable
performance difference.
... as compared with earlier versions or later versions? I hope it's
getting faster, not slower. :-)
Shane
On Thu, 31 Jul 2003 12:57am, Anthony Baxter wrote:
Anthony Baxter wrote
Updating it by hand to ZEO2 hasn't made all good and happy, though -
the ZEO/start.py includes
import ThreadedAsync.LoopCallback
at the top of the file, but the sys.path magic that makes this
available is inside the main
>>> Anthony Baxter wrote
> Updating it by hand to ZEO2 hasn't made all good and happy, though -
> the ZEO/start.py includes
> import ThreadedAsync.LoopCallback
> at the top of the file, but the sys.path magic that makes this
> available is inside the main() function. Moving the import to
> the li
Jim and Andrew hit the nail on the head - excessive cleverness with
vendor branches here meant that the ZEO directory had ZEO1 installed.
Updating it by hand to ZEO2 hasn't made all good and happy, though -
the ZEO/start.py includes
import ThreadedAsync.LoopCallback
at the top of the file, but
On Wed, 30 Jul 2003 17:21:51 +1000 Anthony Baxter <[EMAIL PROTECTED]> wrote:
> So I see ZEO clients here falling over all over the place under current
> 2.6 with:
>
> 2003-07-30T07:01:04 ERROR(200) ZEO uncaptured python exception,
> closing channel
>
.
. [Explanation of problem snipped]
.
>
>>> Anthony Baxter wrote
> So I see ZEO clients here falling over all over the place under current
> 2.6 with:
>
> 2003-07-30T07:01:04 ERROR(200) ZEO uncaptured python exception,
> closing channel
>
> (exceptions.AttributeError:keys
> [/export/01/zope/dev_ekit/ZServer/medusa/asyncore.py|poll
So I see ZEO clients here falling over all over the place under current
2.6 with:
2003-07-30T07:01:04 ERROR(200) ZEO uncaptured python exception,
closing channel
(exceptions.AttributeError:keys
[/export/01/zope/dev_ekit/ZServer/medusa/asyncore.py|poll|94]
[/export/01/zope/dev_ekit/ZServer/me
12 matches
Mail list logo
