Due to essential maintenance, access to Trados cloud will be unavailable on Saturday 30 August from 00:00 to 12:00 UTC.
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 2950 views
  • Users 0 members are here
Options
Related

In Studio 2017 what is the actual capacity for Translation Memories? "Upgrade Translation Memory" seems like a big waste of time.

Former Member
Former Member

My point is that the whole process is like a big waste of time when the TM is a big one. When you have a small TM (say 100K TUs or less) it's OK.

Case in point, I had a new TM with 1.5 million TUs which Studio 2017 advised me to upgrade ("Upgrade Translation Memory"). This is what happened:

  • The original size was 1.8GB and it grew up to 5.1GB (!)
  • The process took more than eight (8) hours, yes, 8 hours!, in a PC with 8GB memory running Windows 10 Pro with an i5 processor.
  • The upgrade went through all the steps and at the end, even though it showed that the correct number of TUs were processed it stayed there like frozen. I couldn't move on.
  • After restarting Studio 2017 the humongous new TM is practically useless since it takes forever for any search. Curiously enough, the original TM is more useful.

So, my question is: In Studio 2017 what is the actual capacity for Translation Memories? Can you advise on a plug-in or external tool to deal with TM maintenance? By the way, the TM utility within Studio is like a big monolith where navigation is like rummaging through a silo.

Thanks.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Some patience in life is quite useful...
    As for point 1: yes, the TM grows in size, as many additional information is written there. So my 1,4 million TM is 3,4 GB. An EU TM with 1,9 million is 9 GB. But where is the problem here? Not enough HDD space? Buy a new HDD...
    As for point 2: it takes in fact longer than that, on a PC with i7 6th generation, 24 GB RAM and all placed on local SSDs. So patience would be what you needed. Let the process run over night. Then wait until all steps are through.
    Not waiting for the process to finish is the reason for your problem described in point 4.

    There is no capacity limit of TMs afaik. The only culprit is, that huge TMs tend to be slow, especially if located on a network or on a spinning HDD instead of a SSD.

    _________________________________________________________

    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.

  • Former Member
    0 Former Member in reply to Jerzy Czopik

    The process went through ALL the stages and finished them up ALL, but then it stayed there for more than an hour with the "Cancel" button still enabled. Usually, when the process is done, the "Close" button is then enabled. I have plenty of capacity in my HD. I appreciate your answer which seems to be reassuring, but I'm still not convinced Studio can handle huge TMs. It's not the first time I've been through this (disappointing) process. If it was just a matter of patience... but there may be technical issues underlying this whole issue. Coming from SDL, I am not confident I will get a straightforward answer and that applies to a number of issues I have brought to this forum with no useful and straightforward answer. That's my personal experience.
  • 0 in reply to Former Member
    So if the "Close" button was not available, I assume the process was not completely finished.
    In my case it took many hours and I just waited to have the "Close" button. As for the huge TMs - I have some with over 1 million segments, but only use those via Project TM, as such big mamma TMs are indeed to huge for "normal" project work, when I need fast matches. However, the searches in my big TMs still work satisfactory. This was different, when the TMs were stored on a conventional HDD with spinning plates. As soon as I moved the TMs on a SSD, the situation improved dramatically.
    Is your PC a laptop?

    _________________________________________________________

    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.

  • Former Member
    0 Former Member in reply to Jerzy Czopik

    The funny thing is that the original 1.8GB TM, with no "upgrade" works just fine. The search function is fast and I get the information I need. This confirms my point for this post: Running the "Upgrade Translation Memory" process for huge TMs, i.e. more than 500K TUs, may be a total waste of time (and resources). I rest my case.