On Wednesday 29 January 2003 1:37 pm, Mario Valente wrote:
OK. Make sure that the clients are connected to the backend server (the one above) on a private network.
For security or performance reasons?
If you intend to spend some extra money, spend it on a front end load balancer caching system. You would put this in front of your ZEO client machines, spreading the load and caching most of the pages.
I would say that some kind of front end proxy is essential for this setup. There are happy users of Squid, Apache, and Pound.
fast. We've been looking at DirectoryStorage but right now its still not final
FYI, we hit 1.0.0 a few weeks ago.
and we're afraid that at some point (ie large sites with lots of objects) the OS might run out of file handles.
Apart from two lock files, DirectoryStorage only opens file handles momentarily. On some filesystems you may want to be concerned with running out of inodes. On linux I strongly recommend reiserfs, which does not have this problem because it can create inodes on demand. (thanks for raising this concern - I will add these to the DirectoryStorage FAQ)
All images should be stored as External Files (as well as any other BLOBs like PDF files, DOC files, etc).
Im not sure that advice is universally true, unless your blobs are never change or mastered elsewhere. Putting everything in ZODB/ZEO simplifies backups, replication, and distribution of changes. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson