Studio 2019 slow responsiveness with TM stored on remote network location

Question

Has anybody else experienced very slow performance in SDL Studio 2019 when your project TM is located on a network path? 
 The network path is mapped to my PC and the network is fast in general, but when I try to commit a segment, Studio 2019 freezes for up to 5 minutes at a time and sometimes even crashes entirely. 
 It's not an issue specific to one TM &ndash; it is happening for all projects. 
 Moving the TM to my desktop helps, but the TMs have to be stored on the network to ensure access by others when necessary, as well as to ensure that it is backed up during the nightly backup cycle. 
 Does anyone have any recommendations?

Paul · Answer

Sinéad Healy 
 Sinéad Healy said: Does anyone have any recommendations? 
 Yes... invest in SDL GroupShare. 
 It sounds as though you need a proper server based solution to be able to work on a TM with multiple users. If you share a file-based TM you can expect problems like this especially as the TM grows in size, and you're also risking corruption. 
 One of the things people like about Trados is that it is possible to share a TM like this which is not so simple to do with other tools, but you have to accept some problems if you do it. Perhaps it's worth reviewing how you use them. For example, do you always create Project TMs for your projects or do you work with the Main TMs? If you don't then I'd recommend you try it... that might help as you'll be working with smaller TMs and only updating the main larger TMs at the end of the project.

Jerzy Czopik · Answer

I am using a similar setup with NAS for years now. Storing any main TM on the network renders this solution simply unusable. The only solution that works in this circumstances is storing ALL project files on NAS, but ALL TMs and TBs are stored locally on the fastest SSD you can get - preferably on a M2-SSD. I use project TMs for all my projects, so the projects can be accessed by anyone who has the same path to main TMs on his/her machine (the main TMs there do not need to be actual, only the names must fit). In case someone accesses the project, the project TM is working, not the main TM. This is fast enough to be able to work. 
 Keeping TMs on NAS or in the cloud is not a solution for sharing these. As Paul says, in such case you need to go for Group Share. Studio Freelance or Professional is a desktop tool, NOT developed for sharing any resources.

Trados Studio > 1. Trados Studio

Studio 2019 slow responsiveness with TM stored on remote network location