We're looking at 10-100 billion tx per year stored and performed. Partly I'm trying to gauge where the dividing line is between using the ZODB and not, and also estimate how many server instances should be running.
> -----Original Message----- > From: Andreas Jung [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 19, 2006 1:29 PM > To: David Johnson; firstname.lastname@example.org > Subject: Re: [Zope3-Users] Zope 3 Capacities > > > > --On 19. Januar 2006 12:26:42 -0600 David Johnson <[EMAIL PROTECTED]> > wrote: > > > I'm trying to scope out Zope 3's capacities. Does anyone have a large > > ZODB? How big is it (in terms of objects)? Any performance issues? > > Does anyone have a very high volume site? What kind of volume with what > > kind of degree of application logic? > > > > > > > > What architectural things have affected performance? I general we're > > looking at using an RDBMS, but we're trying to get a better feeling of > > when we can use the ZODB and when we should stick to the RDBMS. I like > > the ZODB because of it's versioning information in particular. > > > > > > > > We have various datasets: > > > > 1. Transactions: 10-100 billion objects > > per day, month, yr? > > > 2. Users: 10-100 million objects > > up to 1-2 million objects seem to be common for large sites nowadays > > > 3. Contacts: 100,000 objects > > 4. Customers: 100-1000 objects > > Possibly you might consider a hybrid solution using the ZODB and a RDBMS. > > -aj _______________________________________________ Zope3-users mailing list Zope3email@example.com http://mail.zope.org/mailman/listinfo/zope3-users