It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×118
×15
×14

question asked: Feb 05 '13, 8:26 a.m.
question was seen: 5,681 times
last updated: Feb 11 '13, 2:32 p.m.

Related questions

Errors while importing code from SVN to RTC of size 22GB

0
Rao Shines (159●4●51●62) | asked Feb 05 '13, 8:26 a.m.
 Hi,

We are importing source code from SVN to RTC.The code is of 22GB and has 22000 changesets in SVN, the SVN dump is being created successfully but when we import to RTC using Eclipse Client its throwing errors like below:

"An internal Error has Occured

Animating rectangle
Import from SVN
Update Progress

Java.lang.outofmemory error"

We have diskspace of around 100GB available on the drive and RTC workspace created on the same drive

Any help to resolve this is highly appreciated or do we have any better approach to migrate code of huge sige from SVN to RTC

Thanks in Advance

Teja. 

One answer

Most liked answers ↑|Newest answers|Oldest answers

2
permanent link
Matt Lennon (612●2●5) | answered Feb 05 '13, 9:02 a.m.
JAZZ DEVELOPER
edited Feb 05 '13, 9:03 a.m.
Hi Teja.

Large imports like yours can consume a lot of JVM heap space. Increase the JVM heap for your RTC Eclipse client by editing the "-Xmx" line in the <RTC-install-dir>/client/eclipse/eclipse.ini file. It's 512 MB by default - you may need 8 GB or more:

     -Xmx8g

You'll need to perform this import on a 64-bit machine with plenty of RAM and a 64-bit JVM. Otherwise, you're limited to less than 2 GB of JVM heap, which is not enough.

Let me know if this works.

      -Matt
Comments
Matt Lennon commented Feb 05 '13, 9:08 a.m.
JAZZ DEVELOPER

Great article on importing SVN data into RTC:
    https://jazz.net/library/article/650/

Rao Shines commented Feb 05 '13, 9:27 a.m. | edited Feb 11 '13, 2:30 p.m.

 Thanks Matt,


Will make the changes and try, its 64-bit machine with 8GB RAM..

1
Matt Lennon commented Feb 05 '13, 9:44 a.m.
JAZZ DEVELOPER

You'll need more than 8 GB RAM. In general, your RAM should be at least twice your JVM heap to avoid excessive paging and poor performance.

Rao Shines commented Feb 06 '13, 5:01 a.m. | edited Feb 11 '13, 2:30 p.m.

 We have limited RAM of 8GB on the server and cannot be extended.....We are planning to follow the incremental approach of taking SVN dumps with revisions of finite length....


Is this approach is recommendable or do we have any alternate approach...

Tim Mok commented Feb 06 '13, 9:37 a.m.
JAZZ DEVELOPER

I think the incremental approach is acceptable. You can run the import again and it can determine the revisions that have already been imported and continue.

The article that Matt linked also has a section about configuring the memory usage during import: https://jazz.net/library/article/650/#Configuration_the_memory_usage_d

Matt Lennon commented Feb 06 '13, 9:50 a.m.
JAZZ DEVELOPER

With 8GB of RAM, you can probably set your JVM heap to 6 GB for this import operation ("-Xmx6g") as long as there aren't any other memory-intensive applications running on your system at the same time.

Rao Shines commented Feb 06 '13, 12:50 p.m. | edited Feb 11 '13, 2:30 p.m.

 Thank you for the response.....


Is it advisable to take complete dump of 22GB and do incremental import to RTC like 0 to 2000 Revisions for first time and then 2001 to 5000 revisions for 2nd time or

Is it suggested to take SVN Dumps directly in incremental order like Dump1 for 0 to 2000 revisions or Dump2 from 2001 to 5000 revisions..... In this approach not sure if RTC accepts into same component....

In this time we will also try other options and update..

Thanks,
Teja.

1
Tim Mok commented Feb 07 '13, 11:24 a.m.
JAZZ DEVELOPER

I suggest specifying an endpoint just so the import runs successfully instead of running out of memory.

RTC definitely can import the next set of revisions into the same component. You'll have to run multiple imports anyway when you import any tags and branches. Take a look at the article that Matt posted for more details.

Rao Shines commented Feb 11 '13, 2:24 a.m. | edited Feb 11 '13, 2:29 p.m.

 Hi Tim,


Though we are specifying a few revisions to import from the dump, initially RTC creates a complete archive change set for all the 22000 revisions where it is running out of memory.

Is this something expected that RTC first creates the complete archive change set of the dump and imports only the specified revisions... Can we have any option to create and import only specified change sets from the dump?


Thanks,
Teja.

Tim Mok commented Feb 11 '13, 2:32 p.m.
JAZZ DEVELOPER

The wizard has the option of specifying the revision range to import. Did you try any of the suggestions in the article that Matt posted?

showing 5 of 10 show 5 more comments

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.