• State Verified Answer
  • Replies 2 replies
  • Subscribers 433 subscribers
  • Views 1518 views
  • Users 0 members are here
Options
Related

Roll back TM upgrade

David Bequé

Hi everyone,

I upgraded my Big ENNL Reference TM yesterday, thinking it would improve its performance. This took about 10 hours, since it's rather large (2GB, 1,6kk TUs). So far so good, except that it has been completely useless since then. It takes ages to "validate and go to next segment",  pre-translating files freezes after a 5 minutes (for a 200 segment file). So far the only solution that seems to work, is to simply disable it.

After taking a closer look, it turns out this TM grew to a whopping 11GB after the upgrade, which is simply not manageable.

Some context: Studio 2017 is fully updated, so is my laptop (Windows 10, 16 GB RAM, 2,5 GHZ). Studio and all its components have been whitelisted in the AV, as well as the sdlxliff and TM concerned.

Since at 2GB, the size of the TM wasn't an issue and everything worked smoothly, I have two questions:

Is there a way to roll back the upgrade?

Also, why did the size increase that much?


Thanks

David
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi David,

    Studio creates a backup of the TM before the upgrade. You should find it in the same folder as the upgraded TM and with a different file type extension. You might have other options:

    - You could disable fragment matching and fuzzy match repair. For such a whopping TM, I guess that Studio performance can only go so far.
    - Instead of upgrading the TM, you could just reindex it. This does not create the upLIFT fragments and as such should not increase the size of the TM too much.

    I would probably play with disabling fragment matching and/or fuzzy match repair first, to see if this brings back the previous TM performance. If that does not work, bringing back the backup TM + reindexing it might be another option.

    Thanks
    Daniel

    Daniel Brockmann
    Team Trados @ RWS

Reply
  • 0
    Hi David,

    Studio creates a backup of the TM before the upgrade. You should find it in the same folder as the upgraded TM and with a different file type extension. You might have other options:

    - You could disable fragment matching and fuzzy match repair. For such a whopping TM, I guess that Studio performance can only go so far.
    - Instead of upgrading the TM, you could just reindex it. This does not create the upLIFT fragments and as such should not increase the size of the TM too much.

    I would probably play with disabling fragment matching and/or fuzzy match repair first, to see if this brings back the previous TM performance. If that does not work, bringing back the backup TM + reindexing it might be another option.

    Thanks
    Daniel

    Daniel Brockmann
    Team Trados @ RWS

Children