• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

F@h - how best to set it up for this set of PC's?

NDGeist

Senior member
I've got this 20 CPU Nehalem setup I'm stress testing to see if the motherboard is adequate in terms of quality for us to sell. I've got the non-HT cpu's (too expensive to buy the big boys) and I'm wondering how best to setup Folding to maximize my results.

Currently I'm running 2 instances of the SMP client. It taxes what seems to be 4 cpu's per instance.

My client.cfg:
[settings]
username="myusername"
team=198
passkey=
asknet=no
machineid=1 or 2 depending on which F@H directory

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

Is this the most efficient way to get #'s??

As for how stressful a F@H stress test is, these have already went through 40 days worth of Prime95 swinging from 55C ambient to -30C.

Also, when I made my image, I only had the Folding@home exe and my client.cfg file in the folder, and it appears they all got the same Wu when they booted up, is this bad, and can/should it be fixed?

Thanks,
Chip
 
With 20 CPUs, it seems that you could install 5 instances of the SMP client, each in their own directory. (Be sure to give each instance it's own machine ID)

When you check which work unit, be sure to look at more than the project#. The WUs have 3 identifiers, run, clone, generation. Unless ALL 3 of those numbers match, they are different work units.

Be sure to look through your fahlog.txt file for each instance to see if the work units are finishing. If they are, you have a stable set up.

I don't know if f@h is the ultimate stressor of hardware, but it is a terrific indicator of stability.

-Sid
 
Sorry, i did something dumb there...

It's actually 2 quad core cpu's per motherboard x 10 motherboards. So i'm running 10 actual systems with 8 cores each.

As for the projects all being the same, i went and looked again, and it's only 2 machines that are doing it, and there's a good chance i forgot to delete the other info.
 
Back
Top