You are currently working on UAT 

Studio 2019 TM import

Former Member
Former Member

Hi all,

I recently upgraded to Studio 2019 and am going crazy. The TM import (large .tmx into existing TM of ~ 50.000 segments) is incredibly slow and calculation of fuzyy index statistic is taking 3 minutes per 1.000 segments (Windows 8). What can I do?

Best Dörte

Parents Reply Children
  • Hi Paul,
    Thanks for responding. Afraid I can't share my TM with you as they come from my client. But it is very likely they are full of duplicates etc. like you say. I'll try your idea, but the down side to that is I then lose my own TUs from past translations for the same client. But if it saves time...might be worth it. And I guess I could use both TMs at the same time, the old one and the new one from the client. Since I'm working in 2017 today, I'll try your method on the files that gave me all the trouble the other day and see what happens...to be continued....

    Ruth Krawczyk
  • Hi Paul,

    According to my experiences, this is not a TMX file issue but a Studio 2019 issue. I performed a direct like-for-like comparison using the Upgrade Translation Memory Wizard with astounding results. Using Studio 2014 on an old Windows 7 machine with 8GB of RAM and an old Intel i3 processor, the Wizard imported a 277114KB TMX file in 17 MINUTES producing an SDLTM file of 397480KB. On the other hand, using Studio 2019 with a shiny new Windows 10 machine with 16GB of RAM and an Intel 8th-gen i7 processor, the Wizard imported the identical TMX file in over 13 HOURS producing an SDLTM file of a whopping 1890920KB! Thus, with this direct like-for-like comparison, it's obvious that there is something very wrong going on with the Studio 2019 Wizard! After taking your advice of creating an empty SDLTM and importing the same TMX file into it, this did reduce the time taken with Studio 2019 to 13 minutes, producing an SDLTM file of 499616KB. However, the question needs to be asked as to why the Wizard in Studio 2019 is functioning so poorly and producing such a massive SDLTM file.

    Any thoughts?