[Zope] Reasonable maximum # of objects in ZODB?

[Isokangas, Erik HTC/DE/FRA]

	I can't comment on "maximum # of objects in ZODB" specifically, but
I have recently been playing around with ZCatalog indexing.  I now have a
catalog indexing 700,000 documents (although the actual documents are in
another database - not in the ZODB).  It works okay but can take from 3-30
seconds to return results from a search (depending on the query).  ...and
yes, my Zope site takes a little while to start up (15-20 seconds),
presumably because the ZODB (catalog) is around 950MB.

	I quite agree with Max M.  Rather than bloating the ZODB with simple
records I'm now looking at using a separate database server for indexing.  

	You need to find the right mix of ZODB and relational databases
(probably on different servers) to get the "best of both worlds".

	Erik.

> Date: Tue, 30 Jul 2002 00:34:53 +0200
> From: Max M <maxm@mxm.dk>
> To: VanL <vlindberg@verio.net>
> CC: zope@zope.org
> Subject: Re: [Zope] Reasonable maximum # of objects in ZODB?
> 
> VanL wrote:
> 
> > I am trying to convince my boss to go with a Zope-based solution for a 
> > web app.  I had heard that the ZODB scales to about 5 million objects 
> > (products and text files, mostly) with reasonable performance.  Is 
> > this right?  What are reasonable performance and size limits for the 
> > ZODB on single-proc intel server hardware?
> 
> 
> The Zodb is best suitet to complex objects that would be hard to 
> implement in a relational database. Usually you don't have many of those 
> in the database at a time.
> 
> When you have a _lot_ of objects they are usually similar and better 
> suited for a relational database.
> 
> Using Zope does not mean that you cannot use a rdbm system also.
> 
> Rather you have the best of both worlds.
> 
> And you are not gaining in complexity as the simplicity gained by going 
> all relational is quickly lost when trying to implement complex objects 
> with on top an rdbms.
> 
> regards Max M
> 
>