Christoph Berendes wrote:
Why so many, in separate files, you ask...
1. why not? (what's the cost/risk of multiple Data.fs files and mount
points), hmmm?
Because it's not a common use case, so you end up pushing limits and
bumping into bugs that no-one else cares about ;-)
2. makes it
Christoph Berendes wrote:
I am writing to tap the list's experience with running a single zope
instance with a large number (30, 500, 2000?) of mount points.
Why do you want so many ;-)
We're hosting a number of client sites, and for each client, e.g.
clientX, we have a mount point:
Why so many, in separate files, you ask...
1. why not? (what's the cost/risk of multiple Data.fs files and mount
points), hmmm?
2. makes it easy to move a single client site between instances and
servers (we don't yet know how load is going to mount up, and whether
we'll need to set up a
I am writing to tap the list's experience with running a single zope
instance with a large number (30, 500, 2000?) of mount points.
We're hosting a number of client sites, and for each client, e.g.
clientX, we have a mount point:
zodb_db clientX
mount-point /clientX
filestorage
path
