Hello Keenan Cooper

As a former translation project manager running projects in Studio, I have experienced similar situations.

I see in your report that there are multiple files in your project. Studio analyses / pre-translates each file one after the other, looking up one memory after the other, thus this process can take longer in case more files and more TMs are involved in general.

However, 40 minutes for the pre-translation of 7 files seems quite long even with the above in mind. And considering that the report is not saved, there might be an underlying issue in your Studio.

If you analyse the files only, how long does it take? With these 7 files and 3 TMs. Could you please confirm?
Also, is the project also located on your hard drive?

Hoping to hear back from you.

Best wishes,
Greta

Greta Magyar - Customer Success Consultant - SDL

Hello Keenan Cooper

As a former translation project manager running projects in Studio, I have experienced similar situations.

I see in your report that there are multiple files in your project. Studio analyses / pre-translates each file one after the other, looking up one memory after the other, thus this process can take longer in case more files and more TMs are involved in general.

However, 40 minutes for the pre-translation of 7 files seems quite long even with the above in mind. And considering that the report is not saved, there might be an underlying issue in your Studio.

If you analyse the files only, how long does it take? With these 7 files and 3 TMs. Could you please confirm?
Also, is the project also located on your hard drive?

Hoping to hear back from you.

Best wishes,
Greta

Greta Magyar - Customer Success Consultant - SDL

Greta, 

Thanks for your reply.

The project and all relevant files are stored locally.

I after this pre-translate task, I edited, confirmed, then locked a bunch of 99% matches (cost cutting) then ran 3 analyze batch tasks with different analyze settings for a formal estimate. 1) Report cross reference repeats,  2) don't report cross reference repeats, and 3) report locked segments separately). Here are the results:

1) 70 minutes, 10 seconds
2) 36 minutes, 26 seconds
3) 42 minutes, 2 seconds

Based on your statement about multiple files being a potential reason for taking longer, the first report makes sense to be longer than the others since it's looking for cross-file repetitions. But 70 minutes is still epically long. 

Your thoughts, or anyone else's, are welcome.

Wow

so this is strange then right? I have no frame of reference outside of my company. I asked my other teammate to do the same task on his computer and it took 57 minutes and his computer is a beast. 

Any ideas anyone? ?

Hello Keenan Cooper ,

as this thread has been open now for quite some time and with very little feedback and without being able to test the exact same files, this is difficult one to resolve..

I suggestion might be to split the files and run the process again to see if there is a specific file embedded there somewhere which is causing the slow tasks.

Another one of my coworkers if having this same problem. It cannot be a hardware problem because he tried the same pre-translate task on a beastly workstation and the process still took over 40 minutes. There is no specific file causing the problem because our files are not common. We do not have a maintenance plan nor will get one in the foreseeable future.

Hello Keenan Cooper

This might be a long shot but could this maybe help with your analysis?
https://community.sdl.com/product-groups/translationproductivity/f/studio/25740/is-studio-2019-or-2017-too-slow-here-s-a-trick-to-fix-that

Best wishes,
Greta