Loading Server Data : The time, until TMs are loaded in studio client is not acceptable

Hi,

we are having severe issues when loading Translation memories from GroupShare server. The loading time is tremendous, even with approx 1800 TMs on the server, it takes around 4-5 minutes with full Admin account and around 3 minutes with Translator account, until you can see TMs from Studio Client and can open it or link it in project.

I am just wondering if someone around experienced same behavior and what you did to improve performance. According to perf. monitoring on SQL server the Memory and CPU is basically "bored", does not show any significant activity.

Our setup is pretty standard, 2 VM's: Application server (4 cores, 16 GB RAM) + SQL Server (32 Cores, 64 GB RAM)

Version: GS 2017 CU4 (the latest) and Client 2017 SR1+CU6

Any thoughts?

Thank you and regards,

Fana

Translate

Rate translation

Suggest better translation

Raphael Batel over 7 years ago

We are aware that loading the full list of TMs can take a bit longer.
Development is looking into improving this.
4-5 minutes for 1800 TMs seems longer than what I would expect in general though.
Possibly the specific structure of your data causes the list to load slower - or there are database locking issues.
We could look at the details of why it takes even longer for you in a support ticket.

Alternatively, you can wait until general improvements are in place and see whether those address the issue for you as well.

Kind regards,
Raphael Batel | Support Engineer | SDL
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Frantisek Spicak over 7 years ago in reply to Raphael Batel

Hi Raphael,
I am sorry i overlooked your answer. I already addressed this to Phillip Maieski. By the way, I can see same behaviour with new installation, where i create 1800 TMs and i leave them empty. They reside in Root organization.

Could you please tell me more about the "general improvements"?

regards,
Fana
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Frantisek Spicak over 7 years ago in reply to Frantisek Spicak

We installed 2017 SR1 build to see if the performance is better, as far as i can tell, after first observation, there was not done any improvement from SDL.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
kevin spence over 7 years ago in reply to Frantisek Spicak

We have a similar number of memories but we are seeing 3 or 4 times better performance than that when it comes to loading the TM list, the situation improved with one of the Studio 2017 client releases in Q4 last year as prior to that we had a similar problem or simply that the TM list wouldn't load at all, we are currently using GS 2017 CU5 not SR1. In terms of differences vs your selt up we do have each set of customer memories stored together in different server locations and containers so perhaps this helps the mapping process? We have an SSD on the database side which may also make a difference and we have more RAM.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Luis Lopes over 6 years ago

Hi all,

Loading large amounts of TMs in Studio has been optimised since the Studio 2017 CU08 update late last year.

If you still have issues in this area it would be great to send these through our support teams so we can optimize where needed.

Thanks,
Luis

Best regards,
Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados GroupShare > 1. General

Loading Server Data : The time, until TMs are loaded in studio client is not acceptable