[Zope] FileSystem Storage

[Jason Spisak]

John:

> I've been sorta following this conversation for a bit now.. Now I'm not a
> python/zope expert, nor a filesystem expert, and I haven't even looked at
> the code.. but I do see a couple things that could be wrong with this
> approach..
> 
> 1. Number of file handles.. 

As far as I know, this is an OS limitation.  64bit os and filesystem like
XFS has more than enough handles.

>More resources required.. 

What exactly do you mean by more resources?  I am just talking about the
exact same data for an object stored in the current configuration, only
split into multiple files.

>What happens when
> several 1000 objects are needed to be access, and you have to close some of
> the ones you have open? More complexity.
> 2. amount of time determining which file to open/access.. With only having
> a single file, you don't have to make any desicions. Speed by simplicity.

True, but object caching happens now with the ZODB. How does Zope know
"where in the Data.fs file" to find a specific object?  It can't be any
more of a laborious process in a 2 GB ZODB than finding where on the
filesystem a particular file is.

All my best,


Jason Spisak
CIO
HireTechs.com
6151 West Century Boulevard
Suite 900
Los Angeles, CA 90045
P. 310.665.3444
F. 310.665.3544

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.