• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Notfreds kills my gpu clients

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Roisen

Member
Joined
Feb 13, 2007
Location
Folding in Ames, IA
When I'm not running notfreds or the windows SMP client, I get about 3200 from each of my GPUs. When running the windows SMP client, each of my GPUs put out about 3000. When running notfreds, I get about 300 (three hundred) from each GPU.

I've tried setting the VM to lowest priority in task manager, and have set the GPU clients to low in the config, and I've even tried setting them to very high via task manager.

I really like the PPD that notfreds puts out - 1900ppd compared to 900 for Windows SMP, but not at the cost of 6000ppd from my GPUs.:rain:

Has anyone encountered something similar?
 
Post up your version of Windows, and are the gpu's the 9600GT's?

What drivers are you using for the gpu's? Do you have the affinity locked on any of these clients?
 
Also in your Folding.vmx file have got thes lines added to it,

priority.grabbed = "normal"
priority.ungrabbed = "idle"

Set in Task Manager also [email protected] to use both cores and
Set FAH_core_11 or FAH-Core_14 to use one core each, and even try with them set at both cores,

I had to play around to see which was the better and funny enough on Two C2D,s I have that were diferent so you may have same or dif result too!
 
Some rigs have sparkling results adding these tweaks. Others not so much, despite having very similar set ups.

By all means, give them a try. When I was using NotFred's on Win 7 7100, it showed some decrease in the other folding clients, but nothing this drastic.
 
Didn't go well.

In addition now the windows smp client causes the gpu clients to nosedive, so there's probably something bigger going on here. Meh time for a reinstall anyway as soon as I can scrounge up a key from msdnaa.
 
post up your client.cfg and your .vmx file. If you get the priority right, it pretty much has to work. I might add that, if you open the VM and have mouse and keyboard context in it, the VM will run at normal priority and steal all the cpu cycles from the gpu. I don't currently have any notfreds instances going so I can't test it, but I think if the VM is left open, notfreds grabs the VM when it posts error messages to the screen, which is a very regular occurance even when it is fully functional (end of device bug). Keep the VM minimized to avoid this.
 
folding.vmx:
Code:
#!/usr/bin/vmplayer
.encoding = "windows-1252"

# This is a Workstation 5 or 5.5 config file
# It can be used with Player
config.version = "8"
virtualHW.version = "4"

# Number of virtual CPUs. Your virtual machine will not
# work if this number is higher than the number of your physical CPUs
numvcpus = "2"

# Memory
memsize = "1024"

# Selected operating system for your virtual machine
guestOS = "other-64"

# displayName is your own name for the virtual machine
displayName = "Folding@Home"

# These fields are free text description fields
annotation = "Diskless Folding@Home"
guestinfo.vmware.product.long = "Diskless Folding by Nick Reilly"
guestinfo.vmware.product.url = "http://reilly.homeip.net"
guestinfo.vmware.product.class = "virtual machine"

# First serial port, physical COM1 is not available
serial0.present = "FALSE"

# Optional second serial port, physical COM2 is not available
serial1.present = "FALSE"

# First parallel port, physical LPT1 is not available
parallel0.present = "FALSE"

# Settings for physical floppy drive
floppy0.present = "FALSE"

# Logging
logging = "FALSE"

# These settings decides interaction between your
# computer and the virtual machine
isolation.tools.hgfs.disable = "FALSE"
isolation.tools.dnd.disable = "FALSE"
isolation.tools.copy.enable = "FALSE"
isolation.tools.paste.enabled = "FALSE"

# First network interface card
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.connectionType = "nat"
ethernet0.addressType = "generated"
ethernet0.generatedAddressOffset = "0"

ide0:0.present = "TRUE"
ide0:0.fileName = "folding.vmdk"

ide0:0.redo = ""

# Clock is in UTC
rtc.diffFromUTC = 0

extendedConfigFile = "folding.vmxf"

virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "manual"

ethernet0.generatedAddress = "00:0c:29:69:c0:64"
tools.syncTime = "FALSE"
uuid.location = "56 4d 2e 8f f5 b5 b3 cc-2c 58 6b 40 28 69 c0 64"
uuid.bios = "56 4d 2e 8f f5 b5 b3 cc-2c 58 6b 40 28 69 c0 64"
vmotion.checkpointFBSize = "19202048"

priority.grabbed = "normal"
priority.ungrabbed = "idle"

If you mean the client.cfg from the windows smp folder:
Code:
[settings]
username=Roisen
team=32
passkey=
asknet=no
machineid=5
bigpackets=big
extra_parms=-smp -verbosity 9 -forceasm
local=43

[http]
active=no
host=localhost
port=8080
usereg=no

[clienttype]
type=3

[core]
addr=


GPU0
Code:
[settings]
username=Roisen
team=32
passkey=
asknet=no
machineid=2
bigpackets=big
extra_parms=-gpu 0 -verbosity 9 -local
local=518

[http]
active=no
host=localhost
port=8080
usereg=no

[clienttype]
type=3

[core]
priority=96
addr=

GPU1
Code:
[settings]
username=Roisen
team=32
passkey=
asknet=no
machineid=4
bigpackets=big
extra_parms=-gpu 1 -verbosity 9 -local
local=424

[http]
active=no
host=localhost
port=8080
usereg=no

[core]
priority=96
addr=

[clienttype]
type=3
 
Last edited:
client.cfg from the gpu folder. You aren't attempting to fold Win SMP + VM/Linux SMP + GPU on a dual core are you?
 
OK, you have the priority set correctly on the VM and gpu 1, so I'll assume you've also got it right on gpu 0. It should work if the VM isn't grabbed. Any chance that is the problem, the VM window left open?
 
Back