[ZODB-Dev] Re: PartitionedFileStorage

[Shane Hathaway]

On Sat, 26 Apr 2003, Myroslav Opyr wrote:
> I'm going to try it.
> 
> If we started speaking of suport. Can we have compatibility map 
> somewhere? For example compatibility with 2Gb barrier. We ran into a 
> problem when having  installed ext3 partition and having compiled Python 
> to support longfilenames. It occured that ext3 still has 2Gb limit. Look 
> like FAT32 has the problem and ext2 has the problem. NTFS, reiserfs 
> doesn't have it. You mentioned alternatives. It would be cool to have 
> them in one central place dedicated to 2Gb problem. If anybody can 
> provide me with his experience in the problem, I'd volunteer in creating 
> and supporting such central place.

There's no need.  The current "stable" choices for maintaining databases
larger than 2 GB are:

- BDBStorage, which works quite well now and is likely the most scaleable
solution (I presume it could survive well into the TB range), but it
requires periodic maintenance and AFAIK it's not easy to use on Windows;

- DirectoryStorage, which works well if your filesystem can handle hoardes
of small files;

- Get your kernel, filesystem, and Python to support files > 2 GB;

- Use OracleStorage, which isn't very speedy;

- Mount databases to split up storage into multiple files; or

- Use PartitionedFileStorage.

The advantage of PartitionedFileStorage is that it's just as easy to use
as FileStorage.  It creates multiple files only as needed, so you can
forget it's there.  It's only a small step above FileStorage, though, so
don't use it to store 100 GB.

Shane