Re: large db/revs files

Thanks for everyone’s replies.

Took me a couple days to review the links everyone sent.

Thorsten’s links sent me to several of your posts, Mark -- thanks. Based
on your feedback it appears the new release of svn within a month or so
should resolve the problem. It appears the best solution is to wait until
then.

But, I did want to follow-up on the questions Thorsten & Olli had. Here is
an example of our directory structure:

projectA/
         trunk/
         tags/
           release100_06062013_0809/
           release100_06062013_0810/
           …
         branches/

The tags are at the same directory level, which supports the inclination
you had, Thorsten. I wasn’t aware that tagging a directory replicates the
complete directory structure in db/res, which contains the largest files in
our repo. The other directories are reasonable. The source of the largest
db/rev repo, which has 141,573 revisions, is 780K.

If I understand the skip-delta cost, which I may not completely, it sounds
like each tagged release based on the trunk will occupy more space as it is
farther away from the trunk revision number?

Thanks.
André Harper
Received on 2013-06-06 14:56:38 CEST