RQM export takes too long: is there any way to tuning repotools for RQM export?

Don Yang (7.7k●21●108●137) | asked May 13 '13, 6:50 a.m.

Our current RQM 2.0.1.1 fixpack 3 database is 70GB, the extract took
50+ hours.

We will still need to run the import and then the upgrade to 3.0.1.5
and upgrade again to 4.0.2. If the first step took 50+ hours we will not
have a large enough outage window for the change and upgrade. The
straight Oracle dump took less than 1 hour.

The VM running the extract has 32 GBR RAM ad 8 cpus, test to the shared disk
we can write 10 - 20 mb / second.

1) as per http://jazz.net/library/article/206 which is for RTC upgrade benchmark(from 1.x to 2.x)
it suggests the import should be estimated as 3 times of export, does that apply to RQM migration or not?
Is there any benchmark for RQM upgrade?

2) More importantly, is there any way to tuning the RQM export/import repotools to reduce the time?

Any suggestions are appreciated.

Accepted answer

permanent link

Vidya Malkarnekar (1.0k●1●5) | answered May 13 '13, 1:16 p.m.
JAZZ DEVELOPER

Yes, RQM import can take between 3-4 times of export.

It's highly recommended to use RQM 2.0.1.1 iFix5 as it has many performance related fixes for repotools -export.

You should also consider collocation, having RQM on same machine as database server. That

drastically reduces the time but can be hard on drives, space, memory, and processor. At the very least, make sure the network latency between database server and RQM server is minimal.

Don Yang selected this answer as the correct answer

Comments

Don Yang commented May 13 '13, 8:36 p.m.

Thanks a lot for the info.
Checking ifix 5 release and notice a lot of info is there on performance improvement for repotools -export/import.

It's all about the answers!

Related questions

RQM export takes too long: is there any way to tuning repotools for RQM export?

Accepted answer

Your answer