I was wondering if I could get some feedback on DirectoryStorage as compared to FilesystemStorage, which ships with the default Zope product. From what I've read on the website (http://dirstorage.sourceforge.net/), it claims to be a much more robust and fault tolerant way of storing data compared to FilesystemStorage (Data.fs). I hadn't given DirectoryStorage much thought until I saw that Enfold Systems (http://www.enfoldsystems.com/Products/Server/Features) released their Enfold Enterprise Server as default using DirectoryStorage as opposed to FilesystemStorage. Based on this, I wanted to get some feedback from the Zope community about this storage option, it's scalability, it's use in a high volume production setting, it's stability, scalability, robustness, etc. And if the Enfold Systems people are reading this, I'd be interested in their reasons behind their decision to go this route as I'm sure some thought was put into why to go this way as opposed to what ships default with Zope. Our group will be going into production with 2-3 Zope/Plone sites in the very near future and robustness, security, and scalability are key factors in our production environment. What are the community's thoughts on DirectoryStorage as compared to FilesystemStorage? Thanks in advance, Shane -- http://liquid.homelinux.org/
Shane Graber wrote:
Our group will be going into production with 2-3 Zope/Plone sites in the very near future and robustness, security, and scalability are key factors in our production environment.
What are the community's thoughts on DirectoryStorage as compared to FilesystemStorage?
I think it's much of a muchness. A LOT of people care about FileStorage, which means it gets fixed prett yquick if a problem is found. That said, Toby is obsessive about daat integrity and tries to cater for even the worst edge cases. That's probably what you want from the person maintaining your storage code ;-) Personally, I think either is a safe bet... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Sun, Mar 27, 2005 at 05:13:36PM -0500, Shane Graber wrote:
What are the community's thoughts on DirectoryStorage as compared to FilesystemStorage?
Well, FileStorage is a LOT more widely deployed, and most people seem to have no problems with it at all, and it's probably the fastest ZODB storage. BUT it has at times had data-loss problems in some real-world situations. I hit a couple of these, and after a couple very painful POSKeyError experiences, a year or two ago, I switched to DirectoryStorage for everything I care about. I have not lost any data since then. Drawback 1: Some things just take longer. Packing my 2.5 GB DirectoryStorage typically takes an hour or sometimes two! (But uses not much memory.) Ditto for full backups. Drawback 2: You have fewer options as far as the filesystem. I have run DirectoryStorage on ext3, but it probably will not scale. I generally use reiserfs. No idea about Windows. There's exactly one bug with DirectoryStorage that annoys me currently: if running DirectoryStorage on a ZEO server, and the server restarts, you must also restart the clients or else their DSToolkit instances will permanently claim to be disconnected. (This breaks my packing and backup cron jobs.) Probably not a deep problem, but I haven't had time to follow up on it much since reporting the bug. -- Paul Winkler http://www.slinkp.com
participants (3)
-
Chris Withers -
Paul Winkler -
Shane Graber