Tag/branch scalability

What do people think the limits are in terms of putting a really large
number of tags/branches into the repository?

Should I ask this question twice, once for BerkelyDB and one for FSFS?

I once had to ask this same question of the CVS developers. Their response
was something like, "blast away; it may be text based, but it's written in
C and it's very fast. We've done tests with 10 or 20,000 tags and didn't
see much slowdown."

3000 tags later repository operations now take 3x as long as they used to
take, and it's gradually becoming disruptive.

The obvious questions is, why do you need this in the first place? We do a
lot of small release branches, managed using some automation (written
around ant and Tomcat). These branch from a production branch, merge to a
staging branch a few (dozen?) times, then merge back to production again.
Obviously in CVS this requires a tag for each branch and each merge, and
we do two (to mark the event on both the source and destination branches).
I expect this will be simpler in subversion, but nonetheless, the question
remains...

What's the highest number of tags/branches anyone has done so far? And
what happened to you when you did it?

Best regards,
-David

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 24 20:32:30 2004