Problems with large translation memory in Studio 2017

Hello all,

I have a large translation memory EN–SV containing 430,583 translation units I use in Studio 2017. When I upgraded from Studio 2014 to Studio 2017 in January 2018, I had no problems at all with this memory, but later on, one of the cumulative updates changed the situation.

After an update of the memory, it became very large, today 2.14 GB, which is unproportionally big in comparison to my other memories. This memory also slows the software down every time I open the Translation Memories View or the dialog box Translation Memory and Settings for the first time after having launched the software. It looks like Studio is doing some kind of initializing that takes a very long time, sometimes up to two minutes, before I can start working.

The problem is worse on my desktop as it is older and have a slower processor, but it also slows my office laptop down, which has a stronger processor, but not as much as my desktop. I could of course buy a new desktop, but since this memory in Studio is the only problem, I would prefer to solve the problem in some other way.

I have been thinking about exporting the whole memory and then create a new memory, but that will take some time and have to be done overnight. I could also delete some of the older translation units in the memory to make it smaller, but that means I will lose valuable content.

Are there any recommendations in a case like this?

Regards,
Peter Bolin
Sweden

Parents
  • After an update of the memory, it became very large, today 2.14 GB, which is unproportionally big in comparison to my other memories.

    This will be down to "UpLift".  If you see a small triangle next to your TM like this:

    Screenshot showing a small triangle warning next to a Translation Memory (TM) in Trados Studio indicating it has not been upgraded with 'UpLift'.

    It means the TM has not been upgraded and the subsegment matches (known as fragments) have not been extracted and added to your TM yet.  When you upgrade the TM, the triangle will be gone, the fragments are extracted and added, and for a sizeable TM such as yours the end result could easily increase to the sort of size you have mentioned.

    There are two articles here (from the developer) that might be useful for you to read and understand what Uplift is all about:

    https://www.sdltrados.com/blog/tackling-challenges-translation-memory-technology.html

    https://www.sdltrados.com/blog/fragment-matching-translation-memory.html

    It will also show you where the options are and you can try playing with these to see if the performance issues improve at all.  Yo should also have a think about where your TM is maintained.  If it's on a shared drive (OneDrive for example) then this could be a reason for the poor performance since the backing up is not done transactionally as it would be for a true server based TM.  It will be backing up the full 2Gb whenever you make a change.  This can be the cause of performamce issues, and also unexpected results.

    might have some good tips here as I know he works with TMs that are significantly larger than this and has probably ironed out the issues that might have caused him to have severe performance problems.

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:30 PM (GMT 0) on 28 Feb 2024]
  • Thank you, Paul, for your answer. The triangle was visible after the installation of CU 18, so I now have run the command Upgrade Translation Memory. The memory is located on the hard disk of both computers, so that is not the problem. When the slow initializing process of the memory is finished, it performs well on the newer laptop and acceptable on the older desktop. The main problem is that Studio is not responding during about 1 minute on my laptop and during about 2 minutes on my desktop when the memory is in the initializing process.

    This problem affects the overall performance of Studio, since this large memory obviously has to be initialized every time I open the Translation Memories View or the dialog box Translation Memory and Settings. I have to wait 1 or 2 minutes before I can continue working even when I am using another memory and not the large one.

    I will follow your advice and dig into this deeper to see what can be done.

    /Peter Bolin

Reply
  • Thank you, Paul, for your answer. The triangle was visible after the installation of CU 18, so I now have run the command Upgrade Translation Memory. The memory is located on the hard disk of both computers, so that is not the problem. When the slow initializing process of the memory is finished, it performs well on the newer laptop and acceptable on the older desktop. The main problem is that Studio is not responding during about 1 minute on my laptop and during about 2 minutes on my desktop when the memory is in the initializing process.

    This problem affects the overall performance of Studio, since this large memory obviously has to be initialized every time I open the Translation Memories View or the dialog box Translation Memory and Settings. I have to wait 1 or 2 minutes before I can continue working even when I am using another memory and not the large one.

    I will follow your advice and dig into this deeper to see what can be done.

    /Peter Bolin

Children
No Data