• Replies 5 replies
  • Subscribers 431 subscribers
  • Views 2537 views
  • Users 0 members are here
Options
Related

TIP. Speed up Studio 2017 start-up process: I went from 1'40" to only 17 seconds (!)

Former Member
Former Member

I started paying close attention to the Studio splash screen and then I noticed that it usually took about 35 seconds to just load plug-ins and then some other processes before the whole application actually was ready. In my particular case it used to take a whopping one minute and 40 seconds (!) and I was sort of gotten used to that, like, say, "resigned".

Next thing I did was to deactivate some plug-ins. Hey, who needs so many tools and plug-ins to start working in one translation project? Granted, you may need some, but not all the time and in all types of projects. Not to mention that I actually got rid of (uninstalled) some plug-ins. There are some particular tasks that you will do only once in a while, not on a daily basis. Whenever I need, if ever, to run THAT particular task I will re-install the plug-in (which, by the way it'll take less than a minute).

I just wanted to share here that my installation of SDL Trados Studio 2017 SR1 takes now ONLY 17 seconds to load completely! Talk about improvement. Disclaimer: I have a well-maintained PC with 8GB of memory, Intel Core i5, Windows 10 Pro, etc. 

How do you do it? Click on the "Add-Ins" ribbon section, then "Plug-ins" to reveal the form below. You can enable and disable plug-ins to your heart's content. No harm. Share your experience. Thanks.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • Hi ,

    My laptop, similar spec to yours although double the RAM, takes around 17 seconds with all the plugins installed and activated I possibly have a lot more than most users because I test them all the time.

    Great that this resolved the start up time for you but I don't think you found the real source of the problem. I also don't know where to look for it, but as said, it didn't make a difference in his case and I suspect this will be the same for many others too. Always worth a try though if it works for you, but it feels like a workaround to the real issue.

    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

  • Former Member
    Former Member in reply to Paul

    Paul, you tell me about the "real source of the problem". The problem(s)? A memory-hungry, buggy, prone to crash Studio 2017 SR1. The evidence can be read here everywhere in a number of different users posts. The ball is in your court. I have another hint. It comes from a log file (located here: C:\Users\[UserName]\AppData\Local\SDL\SDL Trados Studio\14.0.0.0) called SDL Trados Studio_xxxx.log (there are plenty of them in that folder). I noticed that I get on average 100+ warnings (see example below), the majority of them apparently unrelated to my current Studio set-up. I suppose we, the users, should expect shortly a SR2, which is in order, am I right? Thanks.
Reply
  • Former Member
    Former Member in reply to Paul

    Paul, you tell me about the "real source of the problem". The problem(s)? A memory-hungry, buggy, prone to crash Studio 2017 SR1. The evidence can be read here everywhere in a number of different users posts. The ball is in your court. I have another hint. It comes from a log file (located here: C:\Users\[UserName]\AppData\Local\SDL\SDL Trados Studio\14.0.0.0) called SDL Trados Studio_xxxx.log (there are plenty of them in that folder). I noticed that I get on average 100+ warnings (see example below), the majority of them apparently unrelated to my current Studio set-up. I suppose we, the users, should expect shortly a SR2, which is in order, am I right? Thanks.
Children
No Data