Biggest DBs we see are in the 10GB range. Most are significantly smaller (100s of MB) so I don't think size is an issue. We typically run big persistent caches so I don't think there is much help to be had there. It would only make reads faster anyway right?
-EAD On Dec 7, 2009, at 11:21 AM, Jim Fulton wrote: > On Mon, Dec 7, 2009 at 11:08 AM, Erik Dahl <ed...@zenoss.com> wrote: >> Guys, >> >> Thanks for all the great feedback. Still processing it but here are >> somethings we will try. >> >> We will also >> look at tuning out current ZEO setup. Last time I looked there was >> only the invalidation queue. I poked around a bit for tuning docs >> and >> didn't see any. Can someone point me to them? > > The biggest problem ZODB has in general is docs. > > I'd consider tuning your ZEO client caches and using > persistent caches. > > I'm still curious how big your database is. > >> Our slow loading object was a persistent with a regular list inside >> of >> the main pickle. Objects that the list pointed to were persistent >> which I believe means that hey will load separately. > > Yes. > > Jim > > -- > Jim Fulton _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
