Sorry I was not clear enough. The dedicated ram for the vm is 8 gb
toggle quoted messageShow quoted text
Von meinem iPhone gesendet
Am 04.11.2020 um 23:40 schrieb Shaun Everiss <firstname.lastname@example.org>:
To be honest, if you only have 8gb ram, that may be your issue.
You really need another 8 to work right.
Put 4gb to the ram or 3gb to your vm, and unload anything you don't need and try.
I wouldn't try unless you had more ram.
The cores will be fine, 2 cores to the vm should be plenty.
What you may want to do if you can on the vm is to see if you can get a 32 bit version or even reformat and install a 32 bit os on the laptop then you can dedicate about 3gb to the os and 5 to the vm or have a 32 bit vm and not a 64 bit vm.
You really need another 8gb at least.
On 5/11/2020 10:41 am, Adriani Botez wrote:
Thank you for the hints. Well, the laptop I am using for my work has definitely not 8 cores, it has only 4 and about 8 gb of ram. However, maybe there is some way to at least minimize the latency on the VM.
Von: email@example.com <firstname.lastname@example.org> Im Auftrag von Tim M
Gesendet: Sonntag, 1. November 2020 00:15
Betreff: Re: [nvda] NVDA performance in remote or virtual environments
For what your trying to do make sure the desk or laptop has enough power.
Your looking for CPU's with 8 or more cores and high thread if you go vertual
In either case make sure you have 32 gmb or better.The rest is what you like.
See vm's are power hogs and remotes can have lag. That is why you build for
Then all you have is software issues.
On 10/29/2020 5:50 PM, Adriani Botez wrote:
I thought I start a discussion here on the performance topic in remote
or virtual environments . . .