PDA

View Full Version : GPU2 6.12 Beta 8 - Nvidia


Shiggity
06-24-08, 10:28 PM
Changes:

6.12 Beta 7...

Fixed nVidia FX/NVS detection
6.12 Beta 8...

Support cpu affinity by default, this is related to an nVidia problem and awaits core-side changes.
Fix saving of proxy settings.
Add additional parameters field in advanced preferences - no more shortcut editing!!!
UNSTABLE_MACHINE count reset after a correctly finished WU, for long-running systems
Open configuration dialog box when invalid settings detected
Changes to advanced configuration panel
This will NOT fix problems related to cores of course, like the viewer problems, nVidia desktop lag/lockups, etc.

Enjoy...

6.12 beta 8 (http://www.stanford.edu/group/pandegroup/folding/release/Folding@home-GPU-systray-612b8.msi)

http://foldingforum.org/viewtopic.php?f=43&t=3500&sid=aa32c179a1aa832870e72147a1ee7c56#p33201

I haven't gotten it myself yet, but I'll try it tomorrow, just too tired atm. They suggest un-installing the last version before trying to install this one.

jintatsu
06-24-08, 11:25 PM
anyone tried this yet?

harlam357
06-25-08, 08:58 AM
Not yet... but I will tonight! :)

torin3
06-25-08, 10:12 AM
Running it now, and it seems to have about the same PPD on 5003s.

jonspd
06-25-08, 10:54 AM
gonna wait on doing an update untill the next or official if possible.

LandShark
06-25-08, 01:44 PM
This will NOT fix problems related to cores of course, like the viewer problems, nVidia desktop lag/lockups, etc.

:mad:

dark bishop
06-25-08, 04:12 PM
im wondering if this will work with the 175.16 drivers. i had to get rid of the 177's because they went corrupt and i couldnt game.

Adak
06-25-08, 04:27 PM
I hate it when the drivers go the way of so many politicians! :D :D

dark bishop
06-25-08, 04:32 PM
i know, but atleast reinstalling the 175.16 drivers worked the first time this time.

jonspd
06-25-08, 04:48 PM
I hate it when the drivers go the way of so many politicians! :D :D

lmao nice:screwy::eek:

jintatsu
06-26-08, 02:02 AM
Running it now, and it seems to have about the same PPD on 5003s.

i'll wait for the next update.. :D

drshivas
06-27-08, 10:55 AM
I put this client on a quad running two VMs with an 8800GS @ 700/1800/900, and I am getting 1K ppd more (4926ppd) than my other quad with 2 VMs running another 8800GS @ the same settings, which is yielding 3979ppd. I attribute the gain to the this new feature listed above: "Support cpu affinity by default, this is related to an nVidia problem and awaits core-side changes." I will upgrade the client on my other quad tonight. I doubt this has anything to do with the fact one quad is Vista, while the other is Win2K3 Server.

So it may be worth your while to upgrade to this client if you're running VMs. The ppd drop on the VMs with this client is trivial (<100ppd) after 12hrs according to FAHMon. This is even after deleting the benchmarks.dat to flush the old ppd data.

harlam357
06-27-08, 11:12 AM
So let me get this right... are you running the VMs with affinity set VM1: 0/1 and VM2: 2/3... then turning off the option for setting affinity to a single core on the GPU2 client?

Setup details regarding VMs + GPU2 and affinities please. :)

drshivas
06-27-08, 11:45 AM
On both quads, I have all the VMs set to low priority, and affinities set to 0/1 and 2/3. On the beta 8 client, I don't recall changing the default setting to turn off affinity of the single core. So yes, the GPU2 core does have affinity applied. I'll confirm tonight. I'll also upgrade to beta 8 on the other quad and see if I my other 8800GS gets the 1K boost.

harlam357
06-27-08, 12:08 PM
Ditto on VMs, low priority on both and 0/1 & 2/3 for affinity.

I tried letting the GPU2 client run with the VMs but with it continually getting assigned to Core 3 the SMP client on VM 2/3 stalled. Not to mention the 2/3 VM system clock (time) was all screwed up.

From what I could tell the GPU2 client was using all of Core 3 and not allowing VM 2/3 to get any slice of Core 3.

Do you have your GPU2 core set at idle or slightly above priority?

drshivas
06-27-08, 12:52 PM
Slightly above. That's weird. I'll check my VM times while I'm at it. I don't notice anything screwy, and FAHMon is all green. I assume you're using beta 8?

EDIT: And I assume you have the vmware tools installed to keep time sync'd with the host OS?

harlam357
06-27-08, 02:02 PM
Ok, when I was home I found the option for "Do NOT lock core to one processor"... well, that didn't work either. Maybe it's an issue with WinXP 64-bit? I'll have to install Beta 8 on my E8400 box with XP 32-bit and see if it also wants to grab the last core, and if the option works to thwart that behavior.

No VMWare Tools... I've never had an issue with system times in my VMs. I don't really do anything else with my VMs besides Fold, so I never fooled with VMWare Tools. The issue I saw definitely stemmed from some process/affinity issues. Because until I put the GPU2 in the mix the VMs ran perfectly fine. System time stayed true... no problems.

Also, I see this same core locking problem with Beta 6 as well. Thought it just might be a Beta 8 thing... but it appears in Beta 8 all they did was give us an avenue to do away with that behavior, if only it worked. :-/