Errors while importing code from SVN to RTC of size 22GB
One answer
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
Great article on importing SVN data into RTC:
https://jazz.net/library/article/650/
Thanks Matt,
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.
1 vote
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....
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
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.
Thank you for the response.....
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.
1 vote
Hi Tim,
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?