Could you provide a bit more guidance? Maybe an example. Most people come at ZODB with previous experience in RDBMS.
How do they map SQL INSERT/UPDATE activities to ZODB data structures? In a way that does not create hotspot. A few years ago people would say "pick a BTree implementation that maps to your data structures and use that." But that is naive and pushes the hotspot into the BTree where concurrent updates are happening. cheers alan On Tue, Feb 26, 2008 at 12:42 PM, Benji York <[EMAIL PROTECTED]> wrote: > Kenneth Miller wrote: > > Is there a standard bit of documentation as to how to handle a > > ZEO server with multiple clients writing to the same data structure at > > the same time? > > Not documentation, but there is a standard bit of snark that might be > helpful: "don't do that". ;) > > In other words, the best way to deal with a hot spot is to eliminate it. > That may or may not be possible, but it's a good thing to try. > -- > Benji York > Senior Software Engineer > Zope Corporation > > > _______________________________________________ > For more information about ZODB, see the ZODB Wiki: > http://www.zope.org/Wikis/ZODB/ > > ZODB-Dev mailing list - ZODB-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zodb-dev > -- Alan Runyan Enfold Systems, Inc. http://www.enfoldsystems.com/ phone: +1.713.942.2377x111 fax: +1.832.201.8856 _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev