We located it by hacking the ClientStorage code in order to display the real 
load operations (oids) from ZEO server (cache misses).

I just read again this mail thread. The lack disk I/O surge looks different 
from the symptoms we saw here, so it must me a different issue.

Sorry for the noise.


-----Message d'origine-----
De : Chris Withers [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 20 juin 2006 10:32
À : Pascal Peregrina
Cc : Tim Peters; zodb-dev
Objet : Re: [ZODB-Dev] ZEO LoadEx?

Pascal Peregrina wrote:
> This reminds me something I noticed when we migrated from 2.7 to 2.8

Well, it's 2.7 to 2.9 here, but yeah, it's the same big jump ;-)

> Our issue was a very big PersistentMapping based tree of objects, which was 
> involved in a lot of RW and RO transactions from different Zope instances (we 
> use ZEO of course). There was no miracle to solve the issue; we had to change 
> the structure to BTree.

How come this wasn't a problem with 2.7?

That said, AFAIK, I'm using BTrees everywhere already...


PS: Still, I'm curious, how did you locate the troublesome object?

Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to