Translation memory search slow cancelling

I have a large-ish (guessing) local TM (1.7GB). Doing searches is - as I have complained before - turgid but what I understand even less is why when I start a search and then cancel it, it takes just as long. Almost as if TM insists on completing the search anyway. I just did a search and realised I'd put a typo in it, hit Cancel and it took about 3 minutes before it was done cancelling.

Both issues have plagued me through various versions of Studio (currently 2022) and I have imported/exported the TM at various points without issues, so I don't think it's TM corruption.

Anyone got any thoughts, other than the TM management being generally underwhelming?

emoji
Parents Reply
  • No, virtually all my work falls into the same type of bucket (software localization), it would be nigh on impossible to unpick that into project TMs that give me the same depth of TM. In any case, once it has properly fired up, the speed of searches during translation is ok.

    But that's beside the point. Cancelling a search (and I'm talking about Trados > Translation Memories > select TM > Source Text > Search kind of searches) ought to be a near instantaneous command, irrespective of the size of the file I'm searching through.

    emoji
Children
  •  

    I have no idea how this Trados function (TM Management ⇾ …) looks “under the hood”. If you are willing to try the TM Fusion for Trados app, it does have a search function (“Quick filter”), and the app is very fast. A caveat – when modifying segments I sometimes ended up with corrupted TMs, have not had time yet to find out why. I am just telling you that as a word of caution – try it in a sandbox before you do anything that might cause you grief. There is the option to open a database with read-only access. Not sure what you want to do once you found your segment (copy? edit? delete?).

    emoji