• 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.

Issue with GPU2 Client & XP

lelliott731

[H]ard DCOTM April 2017
Joined
Mar 15, 2002
Messages
941
Ok, currently one of my 8800GTS machines is running on XP, and so it needs a full core to be fed, otherwise it drops down to below 3k PPD. Well I'll set the Affinity to Core 2, and set the Priority to High, and it jumps back up to 5,200 PPD. But whenever a WU is done, it goes back to Core 3, which is what Windows XP uses the most, and the lowest priority.

Has anyone figured out how to get it so that those settings stick? I can't spend the time to upgrade my system to Vista this week, and it's killing me seeing those wasted PPD constantly sitting there.
 
Use the isolate function from SMP Seesaw Pro.
Isolate the GPU2 core on to the CPU core 2.
Move the GPU2 client to join it.
You dont need to up the client/cores priority as now they are the only processes that will use that CPU core.

That how I lock the GPU's client/core to a CPU core.

Luck ........... :D

 
No need. from beta 8, there is a environment variable you can use to set the affinity whatever you want.

 
If I set the isolate function on SMP Seesaw Pro to anything but core 3, after a couple of hours the affinities will automatically reset for some bizarre reason. This is with XP. Same thing happens with my dual quad if I isolate the GPU process to anything but core 7, it will reset after a couple of hours and there's a corresponding massive drop in PPD. That's one reason I just isolate to the default core, which seems to be the highest number.

In any case, I noticed no difference when isolating to core 2, either in PPD or in overall Windows performance. The same slowdowns, freezes and generally sluggish performance on the desktop occurs irrespective of core # isolation. It isn't fun running GPU2 on a non-dedicated machine. Alas, beta software! :(

 
I lost most of the lag on my VM + GPU boxen by isolating the VM's not the GPU client.

First I isolated one of my VM's onto cores 0-6.
Now by setting affinity, I move anything VM related onto cores 0-6.
When the GPU client fires up on core 7, I have very minimal lag.
The slight stuttering when playing a DVD is now the only time it gets annoying.

With any other setting, the box is very laggy.

Luck .............. :D
 
I don't have any VMs installed, so our configs are completely different. The system I use as my main machine isn't one of the dual quads, those are dedicated folders. My primary system is a dual dual-core Opteron and I have one SMP+GPU2 client, that's it. Any other setting besides GPU isolation causes a massive drop in production. Moreover, isolating to any other core besides #3 results in an automatic affinity reset after a couple of hours. The affinity reset also occurs on my other machines... :confused:
 
Back
Top