• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Need VM SMP Help

M

MrBooMY

Gawd
2FA
Joined
Sep 27, 2004
Messages
991
My Virtual Machine is stealing all the processor from my GPU clients even though I set the GPUs to HIGH priority, and the VM to LOW priority. What do I do to stop it?
 
MrBooMY said:
My Virtual Machine is stealing all the processor from my GPU clients even though I set the GPUs to HIGH priority, and the VM to LOW priority. What do I do to stop it?
Click to expand...
What I and some others do is isolate the GPU processes to a single core so no other process competes for access to that core. You can use an app like SMP Seesaw to accomplish this. Keep in mind when you isolate a core to specific processes, no other process will have access to it.
 
That's the problem, I only HAVE 2 cores, so if I isolate it, then it won't be SMP anymore.
 
You can run a dual virtual cpu VM on just one physical CPU core.
The SMP client inside it will slow down around 45-50%, so make sure you can still make the preferred deadline.
I've done that before, when the GPU1 client first came out.

On my GPU + VM boxen, the VM's always run one cpu core short of the total they need.
4x VM's on 7 cpu cores = the clients slow down around 5%.
2x VM's on 3 cpu cores = the clients slow down around 20%.

Luck ........... :D
 
What OS are you using? I've never had a problem with setting the vmware-vmx.exe processes to low priority which allows just about everything else to take cycles away from it. I'm running two VMWare instances on my quad and both are set to low priority. The GPU client I just leave alone because it's useless to change the priority since the core stops and starts each time a work unit is finished and a new one started. Therefore, the priority changes back to the default. However, the VMWare processes will not stop and restart until you reboot the machine or restart the processes so the low priority settings will stay on them. All I do is set those two processes (since I'm running two instances) to low as soon as the machine starts up and both of the processes are listed in Task Manager. I'm currently running Vista64 but it should be the same for XP.

That said, I hate rebooting my machine so this is something I might have to do a couple times a month in most cases.

 
I'm using Windows XP SP3. The first time I set it up I did low priority and it worked. Now it's not for some reason.
 
MrBooMY said:
I'm using Windows XP SP3. The first time I set it up I did low priority and it worked. Now it's not for some reason.
Click to expand...

You have to set the priority every time you reboot and set it on the process I mentioned earlier. It's not something which is "saved" between reboots. I've never had a problem doing this on either OS.

 
I'm not that stupid man, I NEVER reboot my computer unless I have to. I KNOW you have to set it every time you reboot. It's NOT working. When I set it to low with BOTH cores it still takes away most of the processor from the GPU clients to the point it takes like 5 hours to finish their blocks.
 
MrBooMY said:
I'm not that stupid man, I NEVER reboot my computer unless I have to. I KNOW you have to set it every time you reboot. It's NOT working. When I set it to low with BOTH cores it still takes away most of the processor from the GPU clients to the point it takes like 5 hours to finish their blocks.
Click to expand...

You shouldn't be setting anything for any cores. The overall priority should be set for the vmware-vmx.exe process. There should be no setting of cores or anything like that. Just a right click on that process, go over "Set Priority" and select low. You shouldn't be messing with cores or anything like that as it's not needed. If I don't set the priority to low for my VMs the GPU client suffers rather greatly as well as just about anything else that's CPU intensive such as games.

 
You didn't understand me, IT'S NOT F*)@#)@^ WORKING!! I did EXACTLY what you just said. It doesn't work. It STILL takes all but about 3% processor from both the GPU clients. I've even tried setting both GPU clients to HIGH priority, with the VMX thingy set to low, it STILL takes all but 3%. It's like I'm not even doing anything.
 
SmokeRngs said:
You shouldn't be setting anything for any cores. The overall priority should be set for the vmware-vmx.exe process. There should be no setting of cores or anything like that. Just a right click on that process, go over "Set Priority" and select low. You shouldn't be messing with cores or anything like that as it's not needed. If I don't set the priority to low for my VMs the GPU client suffers rather greatly as well as just about anything else that's CPU intensive such as games.
Click to expand...
Do you set the priority level of the VMs in Task Manager, a third-party app or through VMware itself?
 
YES! Everyone seems to think I'm a noob. I set EVERYTHING properly, and it's just not working. It still takes over if I don't limit the VM to 1 processor.
 
You must log in or register to reply here.
Back
Top