[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Suggestion: preventing inode crowding with FSFS

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-10-07 11:59:09 CEST

On Fri, 7 Oct 2005, Kean Johnston wrote:

> > * Provide a Python script to convert an existing repository to the new
> > layout. (An sh script would be simpler, but wouldn't work on Windows.)
> I could do almost all the rest except for that bit. I just
> dont "get" Python (but admittedly havent tried too hard either).
To me this seems more like a nice-to-have than a must-have. You can always
dump/load to get the new format. But it can't be a big script.

> > We might prefer something simpler; I'm not sure if the load-spreading
> > goal of the Squid cache layout is of any great value to a Subversion
> > repository. Also, although 2^64 is "plenty" of revisions, the current
> > FSFS layout does not impose an upper limit on the number of revisions,
> > and it would be nice to keep that property.
> The FSFS layout may not impose such a limitation but the data
> type for a revision does. In fact, it limits it to 2^31 on
> a 32-bit platform or 2^63 on a 64 bit one (its a long int).

Heh, it seems that you could commit a revision per millisecond for some
hundred million years before hitting that 2^64 revisions limit. Greg, is
this only a theoretical concern, or are you expecting bug reports from the
future? :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 7 12:01:17 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.