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

Re: Howto handle remote repository creation in a Multi-Repository scenario

From: Talden <talden_at_gmail.com>
Date: 2007-06-19 23:52:39 CEST

> Example: In my work place the admin took the decision to create one
> repository by team, with all the projects of a team in the same repo.
> With 1000+ revisions it took 3-4 minutes to get any revision graph.
> Last week I migrated a big project of 6000+ revisions from CVS. Now we
> have 7000+ revisions and the revision graph takes almost 15'. Not
> quite usable.

It is a shame that Subversion isn't able to provide revision-graph
information in a usable time-frame (surely some indexing mechanism can
reduce this). Our repository at the time we actively move from CVS to
Subversion (we're in testing and refinement now) will have some 25k
revisions (across two projects).

We decided that we would rather do without the revision graph feature
(or at least accepted that we'll only be able to use it rarely)
however if it meant reducing the efforts of repository management
gaining traceable reuse between projects. If nothing else, just
sharing single imports of 3rd party binaries makes enough of a saving
to make having fewer repositories more attractive.

Your project content may not of course see the same benefits but I'd
be surprised if this freedom to create doesn't in itself introduce
management overhead - what about backup procedures, hooks and access
control - if anyone can create repositories you can be sure that
unnecessary creation might occasionally need deletion as well and you
don't want to allow that to just anyone.

Though I'm not claiming that you are (as there hasn't been enough
discussion to really understand your issues with single repositories
beyond revision graphing), do try not to place significance on the
difference between any two revision numbers other than their order -
they really do work better than the fairly meaningless CVS revision
numbers per file and you don't really get any more useful information
from ensuring that all revisions pertain to a single project.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 19 23:52:45 2007

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

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