• Replies 13 replies
  • Subscribers 434 subscribers
  • Views 6790 views
  • Users 0 members are here
Options
Related

Studio very slow to update main TM

Bruce Campbell

4 minutes to update the main TM with 3 files containing 206 segments, 3124 words!

Studio showing no activity in the Resource Monitor during this time, except for one blip in disk activity I saw when the progress bar lengthened.

Note that this only appears to occur when changes actually have to be made to the TM. If I repeat the update a second time, it completes in a few seconds.

Am I the only one with this problem?

Best regards,
Bruce Campbell
ASAP Language Services
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • in reply to Søren Vedel
    This is simply because of the fragment matching. Extra information is being added to TM. And the UpLift blabla is one of the most interesting new features, providing you new matches composed of fragments from previous matches or matches repaired with your terminology entries. Sometimes, in my GE-PL jobs I get fuzzy matches of 70%+ quality, where I just need to confirm without any changes or the only necessary change is adapt word endings. I would say this is additional leverage of maybe 2% from the TM and more active usage of TB. After having used it for a while, when you are then forced to work with a software, which "nails you on a cross", you notice, how good it is in facht.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • in reply to Jerzy Czopik
    Ok, makes sense. Thanks for clarifying!

    But I have actually switched the fragment matching off, because it apparantly gave bad results in my case. I find Google Translate API with neural switched on terribly good, by the way. Most of the results I have to read twice to find an error.

    But I must try to find a good tutorial to guide me how to use UpLift, and of course, what it actually "is".

    By the way, now we're talking about new features, I saw in the latest MemoQ update a wonderful feature - amongst many other - where I am able to filter my fuzzy results totally the way I wish. E.g. "Show me results between 87% and 92% or whatever range I'd like to filter. Of course combined with the rest of the filter options at the same time.

    Is this possible in Studio? And I guess I should ask this question elsewhere...?
  • in reply to Søren Vedel
    I am not aware to have the possibility to filter the matches that way here.

    Speaking about UpLift: it really depends very strongly on the language direction.
    In my case, GE-PL is delivering really high quality results, while when translating PL-GE the results are more or less not present...
    In a nutshell: the fuzzy match repair feature replaces parts of the current fuzzy match by parts found in other matches (100%, CM, fuzzy, auto concordance) or in termbase.
    So if you have had translated: "Temperature is measured with a thermometer" and have temperature, thermometer, pressure and manometer in your TB, the new sentence "Pressure is measured with a manometer" could be derived from the previous match and TB. In my case this delivers very useful results for GE-PL, which is my main language direction.
    However, all this slows Studio significantly down - so it is simply necessary to experiment, for which jobs/customers it works well and where it is better to switch it off. However, I would never ever resign of this feature. Simply because I'm certain it will be getting better in the next releases.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.