[Zope-CMF] Big CMF sites / Storage

[sean.upton@uniontrib.com]

Eek... I can live with a single ODB, and would prefer it, provided that it
can scale... ;)  There is always the thought of implementing a
portal_catalog replacement that would span multiple catalogs, but I can't
think of a better way to deal with this than lazy concatenation of results,
and I'm not sure that one could make a working tool that way (likely not)...

Chris, you've used both FileStorage and BerkeleyStorage for big ODBs, right?
...for a large DB, which has scaled better for you?

Sean

-----Original Message-----
From: Chris Withers [mailto:chrisw@nipltd.com]
Sent: Wednesday, January 30, 2002 2:12 PM
To: sean.upton@uniontrib.com
Cc: Zope-CMF@zope.org
Subject: Re: [Zope-CMF] Big CMF sites / Storage


sean.upton@uniontrib.com wrote:
> 
> Is this an appropriate method for scaling the ODB for a big content site?
> I'm looking for people's thoughts in terms of implementation issues,
> performance, and reliability of doing something like this?

Things good get real icky. 

Think about the cataloging, which is essential for CMF sites.
My understanding is that objects in one ZODb can't reference objects in
another
ZODB, hence the portal_catalog is gonna get mighty screwed in your
scenario...

cheers,

Chris - roll on ZODB4 :-S