Studio API vs. GroupShare REST API

Hi community

With an automation of Studio 2019 via Studio API running with GroupShare TM-Server 2017 as the main translation provider we sometimes have problems when the server is busy: out-of-memory and translation-provider-threw-error do occur when performing batch tasks like pre-translation or tm-update. If applied manually in Studio, the same batch tasks applied to the same files run smoothly and without error. The same is true if we use file based translation memories runnung with our automation: There will be almost no errors. One suggestion to get better results is to use the GroupShare REST API to communicate with the tm server. But what exactly will be better?  - Less timeout-errors, better management of the server's CPU  and RAM, more instances running smoothly at the same time? 

With kind regards

Victor Linnemann

emoji