• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 47 subscribers
  • Views 1208 views
  • Users 0 members are here
Options
Related

Very slow TM import on GS 2017

Walter Blaser

Hi

We recently moved TMs from a GS 2015 server to a GS 2017 SR1 server.  Because the new server was hosted somewhere else, we exported the TMs on the GS 2015 server and imported them again on the GS 2017 (SR1) server.

We did the import though the web-based management console. The problem we faced is that the import on the GS 2017 server took ages to complete.

Our biggest TM, which contains 550'000 TUs took more than 13 hours to import. Any idea why this is so slow? 

Would appreciate to hear from other users who have done such imports how long they took.

Another thing we realized, which seems to be a bug: even after the background process of the import has completed on the server, the "Elapsed time" count continues to count up. Currently it shows this:

Screenshot of Trados Studio showing an import TMX task with elapsed time of 65 hours 51 minutes 38 seconds, indicating a potential issue with import duration.

 

although the import has finished long time ago.

What is going on here?

Walter

Generated Image Alt-Text
[edited by: Trados AI at 6:31 AM (GMT 0) on 5 Mar 2024]
emoji
Rate translation
×
Suggest better translation
×
  • 0
    Hi Walter,

    It's difficult to say how long a TM import should take as it depends on so many factors, most notably SQL Server performance.
    In our testing the import of 300k TUs took from 25 minutes on a fast SQL Server including SSD drives, to 4.5 hours on a slow SQL Server system, so it varies greatly based on the hardware deployed.
    So 13 hours seems indeed excessive.

    Also due to upLIFT calculations that run overnight, performance can be impacted if an import runs into the upLIFT calculation period. The time period upLift calculations run, can be adjusted in a config file to suit the needs of the GS server environment, by changing the start and end time which are 9pm to 6am by default:

    C:\Program Files\SDL\SDL Server\FGAService\Sdl.FineGrainedAlignmentService.Agent.exe.config

    <workerManager name="BackgroundOps">
    <queues>
    <queue queueName="fga-align" workerCount="0">
    <workerCountRules>
    <rule workerCount="10" from="21:00" to="06:00" />
    </workerCountRules>
    </queue>
    </queues>
    </workerManager>

    As for the UI bug, it indeed looks like a bug, would be great if you could report that through support so they can raise a bug if it's reproduceable.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |