On Monday 05 March 2007 08:08, Malcolm Rowe wrote:
> [Summary: I'd like to implement per-repository options for FSFS, stored
> in a new config file at creation time. Search for 'the plan'
> if you want to know how, or read on if you want to know why.]
>
> I've been thinking a bit recently about FSFS's scalability and
> performance, and there are two non-backward-compatible things that I'd
> like to be able to implement.
>
> The first is the ability to split your revs/ and revprops/ directories
> into separate 'buckets' or 'shards', so that we don't require a
> repository with a million revs to contain a million files in one
> directory.
What I forgot to say: The problem is not only in the revs/ and revprops/
directories, but in the transactions/*/ as well.
If you do a checkin, you get *for each file* a property file and a description
file ... so for 100 files, you get more than 200 files in a single directory.
Now try to commit 150 000 files, ie. a whole system installation.
Even if that's an extreme use-case, imagine having a (previously
mentioned) "bad" filesystem which allows only ~2000 files in there ... you
couldn't do a single commit changing all copyright headers of the subversion
sources.
This could even be done without any compatibility issues, as the transaction
directories are per definition temporary and exclusive.
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 12 11:19:45 2007