It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,789
×11,931
×889
×173
×46

question asked: Sep 24 '12, 5:28 a.m.
question was seen: 5,532 times
last updated: Oct 12 '17, 1:17 p.m.

Related questions

FAQ - How this Forum works

Need guidance for importing a large SVN dump into RTC

0
Philippe Debras (1●1●2●2) | asked Sep 24 '12, 5:28 a.m.
edited Oct 12 '17, 1:17 p.m. by David Lafreniere (4.8k●7)

Hi,

our SVN repository is quite large:
  - SVN dump file is about 105GB
  - we have about 215000 SVN revisions
  - trunk check out is about 12GB
  - we potentially have about 30 branches and tags to import
  - we have about 25 toplevel directories that we want to import in one component each

We made some experiment importing one top level directory from trunk, it took about 12 hours.
We imported the same top level directory from a branch and it took about 6 hours.

Which guidance could you provide in terms of:
  - how to manage a large history
  - whether incremental migration is feasible
  - how to mitigate migration and continuity of service
  - which gain or loss in performance SVN users can expect with such a large code base

Thanks,

Philippe

Accepted answer

1
permanent link
Michael Valenta (3.7k●3) | answered Sep 25 '12, 11:05 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Have you read the article on importing from SVN into RTC (https://jazz.net/library/article/650/)? There is also a planning guide (https://jazz.net/library/article/70) that discusses using svndumpfilter to break the dump up into smaller chunks which may be possible for you if your repo has 2 or more independent projects.

The importer does support incremental migration in the sense that an import can be continued from a particular revision. As for performance, RTC handles large histories well.
David Lafreniere selected this answer as the correct answer

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.