"tp import all" runs 24 times faster than "tp import <TR>" for long queue?

[Former Member]

After a test upgrade to ECC 6.0, I processed 1200 individual transports in 12 hours. When I rebuilt the queue of 1200 transports and processed "tp import all", it completed in 30 minutes.

Should I expect "tp import all" to process 24 times faster than individual imports?

800 transports were client independent (code) and 400 transports were client-specific (configuration).

What run times have you seen?

What problems with "tp import all" have you seen?

Best regards,

Gary Sherwood

[Former Member · Accepted solution]

"tp import all" should be a lot faster becuase objects are collectively activated. If an object is included in several transports, only the last version will be activated.

[Former Member]

Hi Gary

You don't know the 800 transports which are wating for the import, what could be render your system in case of import all. so, that's why , i will prefer to you import individual request instead of import all.

offcourse, Import all are faster than the individual because it prepare all steps once to start import,

Regards

Anwer Waseem

[tombo_larsen]

Hi

A "TP IMPORT ALL" is faster when it processen one PHASE of the import process for ALL request at a time, and then the NEXT phase for ALL transport request. Therefore even when one object/program exists in NORE transport requests, then it is only activated (which takes time) once.

Best regards

Tom