• State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 18 replies
  • Answers 3 answers
  • Subscribers 434 subscribers
  • Views 8813 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Studio 2019: Translation Results lookup horribly slow with default settings

Jędrzej Ilukowicz

Hello,

I installed the Studio 2019 as an upgrade to Studio 2014. Unfortunately, all projects set up with existing TMs (upgraded, of course) and new TMs suffer from a horribly slow lookup of the translation results in the editor window.
I've been struggling with this issue even while processing very short files with TMs storing no more than, say 50 or so pairs.

What gives? Is this the AutoSuggest or something else in the default setup bogging the lookup? I find it extremely inconvenient and unacceptable, especially when compared to the super-fast lookup times in Studio 2014, even with multiple large TMs enabled.


[locked by: Steven Whale at 11:42 AM (GMT 1) on 19 May 2020]
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul
    Yes. I believe it's unrelated to the issue in hand; adding exceptions as suggested above did not resolve the performance issues with the TM lookup in the Editor window.

    I think it might be related to the upLIFT and other automated suggestion functionalities in Studio 2019.
  • 0 in reply to Jędrzej Ilukowicz

     - I found a very similar issue here:
    community.sdl.com/.../9717

    I'll highlight this again - the Avira antivirus which I run is not the issue, I've even tested the performance with the PC isolated from all networks and with the AV completely turned off; the problem persists, all the same for the AV will all the exceptions added as instructed in the KBs you've posted. The Translation Results window shows "Searching..." for over 3 seconds, usually up to 10 or 20, even with two or three-word segments. I didn't see anything like this in Studio 2014.
    Also, the TM is new from scratch and being populated on the go. I've run fuzzy index recompute, to no avail.

    I also noted that when I hold the cursor on a previous segment, and then skip to the next empty segment while the Translation Results shows "Searching...", the search slowly returns a fuzzy match for THAT PREVIOUS SEGMENT, not for the next empty one (which partially matches a completely different source, saved to the project TM, say, 10 segments ago). That is absurd.

    This is unacceptable at work on jobs with thousands of words in partials (I am already behind schedule with a large project and WILL have to pull an all-nighter :( ). I've never seen something like that in the worst-performance CAT tools, like Across with a TM on a client's server and laggy pings on its end.
  • 0 in reply to Jędrzej Ilukowicz
    Hi

    I think it would make sense for you to log a support case for this issue so a support engineer can try to identify what's causing the problem for you. I'd recomend you log a case for this.

    gateway.sdl.com/liveagentlicensing

    You have two options:

    1. Submit a case using a webform
    2. Use live chat to get a licence reset

    You want to use the first option. Make sure you refer to this thread, and also feel free to drop me an email with the case number so I can follow up for you as needed - pfilkin@sdl.com.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    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

  • 0 in reply to Jędrzej Ilukowicz
    Update for today:

    SLD Support replied they can only help me with installation and license reset.
    In other words, I'm left with a major issue that prohibits efficient work in Studio and a kind suggestion to get myself a contract for over 200 EUR. I know, house (seller's!) rules, but it's ca. 250 EUR on top of the 250 EUR I paid for the license. :(
    * sighs *
  • 0 in reply to Jędrzej Ilukowicz
    Hi

    I think was probably a misunderstanding as they should really help with this as it is an installation issue. Hopefully you'll hear from support in due course.

    Paul Filkin | RWS Group

    ________________________
    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

  • 0 in reply to Jędrzej Ilukowicz
    Hi

    Seems it was a misunderstanding as you are reading the automatic reply that all non-SMA customers receive when logging a Case. Your ticket is still open, and one of our engineers will get in touch with you, tomorrow most-likely. In the meanwhile, can you provide a little more background information I can share with the support team before they get to you?

    Are you using data on a shared-drive?
    Have you performed any tests with local TM’s/TB’s?
    Have you disabled look-ahead, match repair and all those bells and whistles?

    This will just help to get an idea where to look before the call.

    Paul Filkin | RWS Group

    ________________________
    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

  • 0 in reply to Paul

     
    1. No. All TBs and TMs are on a single logical system partition which occupies a single physical HDD.
    2. No, see above.
    3. What I did with the TM which revealed the issue was to disable upLIFT and reindex the TM. It changed nothing. What exactly would you suggest to turn off in the Bells and Whistles Department, to restore the neat performance of TM lookup and CM/70-100% match application that I did enjoy in Studio 2014?

    Also, when the Translation Results is sluggislhy trying to keep the pace with me jumping the cursor between the segments in Editor, Studio often freezes and crashes to desktop without any error message.

    Tip: the source document is an XLS spreadsheet with just one column and ten thousand or so rows.
    I'm at row 5000-ish, which is about 4000 pairs in the TM now. The TM was made fresh for the job.
    The context is that many segments are farming equipment part descriptions, so they contain numerical placeables and you can have five to twenty segments with a word or two of any difference in between them. Alas, the TM lookup mulls over a, say, 90-percent match for dozens of seconds before inserting a fuzzy.

    Here's the fun part: I've added a different project with an MS Word file as a source. Three TMs are hooked up, and each has tens of thousands of segments. They're not even upgraded to Studio 2019, and the Translation Results runs like the Roadrunner trying to rile up Wile E. Coyote.
  • 0 in reply to Paul
    Hello,

    Could not reply. I had an accident, so the case opened with Bogdan from SDL support died 'of natural reasons'.
    Since all is fine now, let me sum up what I've found.

    The background of the particular project was a huge XLS file with many segments differing only in two to three words or placeables (they were versions of different technical parts for farming machines).

    You suggested turning off Editor and Batch Tasks in Match Repair Usage under Match Repair in Project Settings. I did that, and voila, worked like a charm.

    I managed to replicate the problem on a similar project with ca. 50 words per segment, and the segments were approx. 70-90 percent fuzzy matched. The solution also worked here.

    Hence, the probable culprit its the upLIFT Match Repair functionality, despite running Trados 2019 on a rig with plenty of headroom in terms of CPU and RAM. Note that the problem occured on legacy TMs (generated with Trados 2014 and earlier versions), both upgraded to Trados 2019 and not upgraded.

    The problem and the solution may seem unusual, as I do not see many complaints about anything similar to what I've encountered.
  • 0 in reply to Jędrzej Ilukowicz
    I have the same issue and it started just randomly in the middle of a 5K project with 3 TM's, everything else (file locations) the same as it has been for years (in 2015 and 2017). I have not used SDL 2019 much yet and only recently updated with SR1. I turned off the Match Repair and this immediately solved the problem. I'll have to look into it more after project deadlines.