usually they makes it "3" times larger without any kind of advantages.
now, it goes worser, "5" times ? Wow.. a.mazing..

I guess, unfortunately, there is NO solution from user side.
Only SDL could solve this silly situation

Good Luck To You

ah..  0.4 Million TU is not a big monstor,  just a cute little baby -.. now it is a troublesome 2 GB teens though.

Peter Bolin

Peter Bolin said:

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:

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.

Jerzy Czopik 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.

I am sorry, I did not digged above two good postings - too Long....
Though
I have a simple question.
Is there any "option" to go back to good old "Much Smaller" TM ?

Thanks

Unknown said:

Is there any "option" to go back to good old "Much Smaller" TM ?

I'm afraid not. The only solution is to recreate the TM and do not upgrade it.  The way to do that is to export to TMX, do not upgrade the TMX as this will only recreate what you had, but rather create an empty SDLTM and import the TMX.  I'm pretty sure this won't initiate the UpLift process.

ah.. that is good enough, I guess

I have imagined that should I made a new TM, than its size getting 3 times bigger than earlier automatically. But, Your explanation is quite different from my wrong imagination.

Thanks !!!

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