You are currently working on UAT 

  • State Suggested Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 6404 views
  • Users 0 members are here
Options
Related

SDL 2019, Windows 10, Parallels 14

scb

Has anyone else installed SDL 2019 SR1 under Windows 10 on a Parallels 14 VM? I have allocated 20 GB of my 40 GB RAM to the VM, which should be more than sufficient. However, I am still experiencing significant speed issues under SDL 2019, which includes frequent crashes. I can only assume that Parallels 14 is causing the problem somewhere, but I have yet to find a solution. I found an earlier entry about "Shared Folders" as a possible issue.

Any thoughts?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Bruce Stout
    Parallels is the standard edition, we have the pro edition only on a shared machine for other reasons.
    The i7 is good for virtualization, 8GB of ram are not enough, you should have 16GB.

    We assigned 2 cores and 4096 of ram. You can maybe bring it up to 6/8GB if you have 16Gb of ram, but there's no need to use so much ram for studio. You won't get much more speed anyway (I think being a 32bit application, it can allocate a maximum of 4gb anyway, or chunks of 4gb, not sure about this).

    There are some tips to speed up windows 10 (windows 8.1 was faster anyway), like optimizing software running at boot, reducing graphical animations, etc, you can find sever well written posts on internet.

    Also you can use "process lasso" that is a software that manages multitasking better on windows and makes things a little snappier with very few bucks (I recommend to always pay shareware and commercial software, developing software is a very expensive and effortful task).

    The october version of windows 10 seems to be slightly faster.

    If I were you I would download the windows 10 ISO and trados installer and build a new machine from scratch, installing parallels tools, without activating, just to see if things runs faster out of the box. At least you should be able to reduce the options.
  • 0 in reply to Enrico Rosso
    also be sure to have an SSD and have a good amount of free space on it (20%+ would be ideal).
  • 0 in reply to Enrico Rosso
    Thanks Enrico, that was about the most helpful advice I have ever had. In retrospect the lack of RAM makes sense. The behaviour of the machine is so idiosyncratic it suggests it is shifting work memory to the hard drive instead of RAM.. something that used to happen back in the old dark days when RAM was super expensive. I'll give it a shot. Thanks again. That was a great reply. Also re Parallels tools. I gave up trying to run the memories on an external server also for speed reasons. Maybe I can get to solve that too.
  • 0 in reply to Bruce Stout

    Bruce Stout said:
    Hi scb. I'm running the pro edition. maybe the issue is just RAM related.

    Definitely!
    Virtualizing an instance of Windows on another OS is like running two computers on one... so, logically, you need a machine with a specs of two (powerful enough) computers... i.e. logically, 8 GB RAM is way under the par...

    As Enrico mentioned, you need at least 16 GB RAM in your main machine and assign at least 4 GB to the virtual machine. And better even more, if you are going to run MultiTerm and other applications in Windows VM as well.