2009/5/26 Pedro Ferreira jose.pedro.ferre...@cern.ch:
In any case, it's not such a surprising number, since we have ~73141
event objects and ~344484 contribution objects, plus ~492016 resource
objects, and then each one of these may contain authors, and fore sure
some associated objects that
2009/5/14 Dganit David dgani...@puresight.com:
We are planning a web application that saves the data of up to 1,000,000
users.
I would like to know the limitation of zodb.
Currently we are using ClientStorage with zeo,
In my experience building a large scale application, ZEO did not
2009/3/31 Sandra elsand...@yahoo.fr
For example, my computer have 1 GB RAM, could i have 2 GB objects loaded in
ZODB memory? I don´t well understand what is the cache in ZODB compared to
the RAM.
A ZODB client has an in-memory cache in RAM, and an optional on-disk
cache. The server stores
On 18/02/2008, Kenneth Miller [EMAIL PROTECTED] wrote:
So i've got my ZEO Server running with two zeo clients. One client is
pouring data into the DB, and the other is looking for it to do something
with it. The problem I'm having is that the second client can't see changes
to the DB after it
On 17/12/2007, Jim Fulton [EMAIL PROTECTED] wrote:
I doubt that taking the database offline would make much difference.
How much memory do you have on the machine?
How much memory did the server process use before packing?
Thanks for your answers (Alan too). The ZEO server is supposed to have
I have a ZEO application, occasionally on shutdown I see an intermittent error:
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
I've got a feeling I've seen this reported before on this mailing
list, and it looks the same as the problem here
Whilst playing around with fsrefs.py I noticed that it always seems to
claim the filestorage has errors, for example after a single commit
through a zeo server it says:
oid 0x0L persistent.mapping.PersistentMapping
last updated: 2006-11-16 15:30:52.943036, tid=0x36994C2E1E3E9DDL
refers to
Ok, I have the asyncore loop in, I've added explicit transaction begin
and aborts, and cleaned up the test case a bit:
import thread
import asyncore
import random
from ZEO.ClientStorage import ClientStorage
from ZODB import DB
from persistent.list import PersistentList
from ZODB.POSException
Hi Alan,
Thanks for the advice. I'm using multiple processes, one on each host
in a cluster. The extra thread is only used to run the asyncore loop,
which allows zodb to receive asynchronous notifications. I've been
playing around with your suggestions, and found that if I don't run
the extra
Hi,
This issue results in a corrupted database. Can anyone confirm that
they can reproduce this with the test case I provided, so that I can
eliminate any potential problems with my setup as being the cause?
Thanks,
Chris
___
For more information
The bug I'm getting on the client side is two or more clients
simultaneously reporting:
Traceback (most recent call last):
File /home/chrb/test_bad.py, line 45, in ?
i = g.index(random.choice(g))
File /usr/lib/python2.4/UserList.py, line 78, in index
def index(self, item, *args): return
Hi, with zodb-3.6.0 I occasionally see the error:
ERROR:ZEO.zrpc.Connection(C):(localhost:12345)
Asynchronous call raised exception: ManagedClientConnection
('127.0.0.1', 12345)
Traceback (most recent call last):
File /usr/lib/python2.4/site-packages/ZEO/zrpc/connection.py, line
421, in
12 matches
Mail list logo
