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

Re: SVN scalability problem as number of tags grows

From: John Coiner <john.coiner_at_amd.com>
Date: Sat, 21 Feb 2009 13:35:27 -0500

Greg Stein wrote:
> It really doesn't have anything to do with tags/ per se, but simply
> that you're creating an ever-larger directory. The size of the
> name:node mapping for the directory contents will continue to grow as
> you add new entries into that directory.

Yes, agreed.

> The sharding is the appropriate solution. You could shard by date,
> initial letters of the tag, or the hash of the tag (as you suggested).
> Just settle on one, and you should be fine.

Thank you, it's nice to have a vote of confidence.

It would be nice if the svn book had a warning about this. It would be
extra nice if the svn book had a section on the scalability of several
common operations.

One of my coworkers has tested SVN scalability in a number of
situations. So the data exists. I'll get in touch with the svn book
project and see if they would like a contribution.

> Another solution would be to delete obsolete tags... Lots of possibilities.

Agreed. It's difficult for us to know which tags are obsolete, which is
our own problem.

Another possibility is to use rev #s rather than tags. If we were
starting over we might do this. (Given our infrastructure already
deployed atop SVN, which already uses tags, switching to rev #s is a
riskier change than switching to sharded tags.)

Thanks for your help with this. Cheers,


Received on 2009-02-21 20:29:31 CET

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.