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

RE: Re: SVN scalability problem as number of tags grows

From: Andy Bolstridge <andy_at_bolstridge.plus.com>
Date: Tue, 19 May 2009 06:54:16 -0700 (PDT)

> 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.)

Someone once suggested storing a 'label' text that mapped to a revnum, so you could have human-readable 'tags' without having to create the tag branches. IIRC he got shot down in flames, but I think the suggestion was a good one - especially if you create many tag branches, and they are not quite as cheap as described.

sure, adding new entries = more data, but if you add more data and branch as well, ad then make lots of tags, you're going to see a significant increase in storage sooner rather than later.

I havn't seen a problem with it yet (and I have 12Gig and 300,000 revisions) but this does act as a warning not to start creating tag branches, thanks.

Received on 2009-05-19 17:37:51 CEST

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