On 14.05.09 08:29, Dganit David wrote:
> We are new to zope,
> We are planning a web application that saves the data of up to
> 1,000,000 users.
This is a pointless number. The estimated total number of objects is
> I would like to know the limitation of zodb.
> Currently we are using ClientStorage with zeo,
> And zeo uses filestorage.
> What are the limitation of using filestorage?
Basically one - expect limitations given by the OS. *Practical*
limitations are introduced when it comes to aspects of packing
and doing backups. A single filestorage should perhaps
not become bigger than around 100GB in order to deal with
packing and backup in a sane way.
> Is there a limit on the number of objects ?
Basically no. Zope maintains an index of all objects in RAM (whose
size is linear to the #objects).
> Is there a limitation of the global size of the database?
> Is there an easy way to split the data using several fileStorage?
Multiple storages can be mounted .
> Do you recommend using DirectoryStorage or any other type of storage.
Consider consulting a Zope consultant with expertise in building large scale
Zope apps. Building an application for 1M users requires careful planning.
Nothing you can accomplish with basic Zope skills. Especially have in mind
that the ZODB is not the best solution for heavy concurrent write
org:ZOPYX Ltd. & Co. KG
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org