[Zope] Zope sizing and Scalability
Wed, 07 May 2003 13:44:53 -0700
Size won't be an issue with DirectoryStorage, but number of objects is a
more important factor... If that 200GB is comprised of lots of small
objects, there are still penalties for storing filesystem metatdata for
many, many files (i.e. tens of millions) - this is why it is recommended to
use ReiserFS with DirectoryStorage.
From: Paul Winkler [mailto:email@example.com]
Sent: Wednesday, May 07, 2003 5:36 AM
Subject: Re: [Zope] Zope sizing and Scalability
On Wed, May 07, 2003 at 09:51:30AM +0100, Chris Withers wrote:
> Andrew Howe wrote:
> >I am looking for some information regarding sizing of the Zope database
> >its scalability, how big it can grow without performance issues
> >beginning to impact on it etc. I have read the documentation in the
> >manual regarding how to set up a number of servers but it does not give
> >any indication as to how big a zope installation can be.
> It sounds like you're talking about ZODB.
> I have a few servers running heavily loaded 2GB Data.fs'es.
> I've heard rumours of 10-20GB Data.fs'es happily in production.
> There's also recorded instances of 200GB Data.fs'es, but I'm more
> about them ;-)
OTOH, a 200 GB DirectoryStorage should not be a problem.
DBTab might be worth a look too, for "mounting" different storages at
different zope folders.
i've never run a storage that big so this opinion is worth the paper
it's printed on ;-)
"Muppet Labs, where the future is made - today!"
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -