Multiple Clients - Vista

[nitrobass24]

Right now I have the x86 gui client installed. I want to add a second x86 client and use the -smp switch so It can use all 8 of my cores.

In Vista it keeps the work folder and stuff in c:\users\*username*\appdata\roaming\Folding@home-x86

I tried to make a new folder in \roaming but there is no way to point the folding@home.exe to the new folder that i can see. I checked the config files...but do these exes not have exe.configs? What language are these written in? Is is open source?

Is anyone else doing this?

 

[APOLLO]

You're running the GUI version of the client? That might explain it. I was under the impression you had the console client installed. DL and install the console version and follow the steps I described in the other thread. If it still doesn't work, hopefully someone with solid Vista experience will reply but at least you can try the console version in the mean time.

 

[wickedld9]

edit: nevermind, nothing to see here.

 

[Sunin]

Definitely kill UAC... when I had it on it would not let me configure the client correctly and even though it showed the MPI installing correctly it did not. Go to control panel, users, turn off User Authentication Control (I think that is what it stands for) and it will force you to reboot... do the install on the mpi and run the -configonly on the client and redo it... then make sure you run it with -smp and you should be happy . I leave UAC perma off.

 

[nitrobass24]

Yea I turned UAC off a long a time ago... i just do to much stuff that requires admin rights...
Ok so here is what I got I downloaded the FAH 6.2 Console MPICH. Installed MPI, ran the config, and started it with -smp. Ive noticed that i seems to be running 4 of the same processes. Should it not be running 8?

 

[capreppy]

It will run only 4 processes per SMP instance. Given that you have 8 cores, to get the best bang for the buck, you'll want to run 4 SMP instances. Generally the rule is 1 SMP instance for C2D and 2 SMP instances for C2Q. Since you're running 2 Quads, you'll want to run 4 instances.

Others will need to chime in here, but I believe Affinity Changer will handle 2 Quads. I don't remember reading anyone using it, but it definitely works on a C2Q.

As for turning off UAC. That is personal preference. If you don't wish to turn it off, you'll need to update the properties for the executable to run as administrator. That takes care of the UAC issue without having to turn off UAC.

edit: version 1.0.5 will handle 8 core computers

 

[nitrobass24]

version 1.0.5 of what?

 

[Xilikon]

Affinity Changer 1.0.5

 

[nitrobass24]

is there a way to have the gui client run on more than one core? I really like the visualizations

 

[Xilikon]

No, you cannot install 4 gui clients. You need to install console clients on the extra cores. You could run 1 gui and 3 console so you can retain the vizualisation for 1 core.

When installing extra clients, make sure the Machine ID is different for each (1 for the GUI, 2-3-4 for the consoles).

 

[APOLLO]

It will run only 4 processes per SMP instance. Given that you have 8 cores, to get the best bang for the buck, you'll want to run 4 SMP instances. Generally the rule is 1 SMP instance for C2D and 2 SMP instances for C2Q. Since you're running 2 Quads, you'll want to run 4 instances.

Others will need to chime in here, but I believe Affinity Changer will handle 2 Quads. I don't remember reading anyone using it, but it definitely works on a C2Q..

edit: version 1.0.5 will handle 8 core computers

Honestly, Affinity Changer didn't work for me when I installed it on my dual quads. Whether they were Conroe or Penryn based processors it didn't make a difference. I tried two, three and four clients concurrently. The highest production in native Windows XP was achieved with three clients and no AC, anything more or less and FahSpy was reporting a net drop in production. I had my systems running that way since last fall. Three clients on my 2.8GHz dual Penryn Xeons were netting ~6200PPD in native XP with P2653 WUs. The production plummeted with the advent of the P2665.

The most production anyone will see on a dual quad is with 4 VMs running Linux SMP clients, but that is recommended only for a dedicated folder. You will not want to allocate that much system memory just for F@H, it would be senseless unless you have 8GB+ of RAM, and the sluggishness is very palpable with so many VMs. Furthermore, the increased production of Linux VMs is only fully realized when all the clients are processing either P2605 or P2653 WUs, any other WUs like the P2665s which my clients are receiving for some reason, and the advantages start diminishing rapidly.

In conclusion, I think several caveats have to be observed with any of the potential configuration scenarios. Dual quads take a lot of tweaking to get the most out of them, and TBH, that has rarely been achieved with F@H. I haven't even mentioned anything about OC, which is another major PIA if at all possible.

 

[nitrobass24]

No, you cannot install 4 gui clients. You need to install console clients on the extra cores. You could run 1 gui and 3 console so you can retain the vizualisation for 1 core.

When installing extra clients, make sure the Machine ID is different for each (1 for the GUI, 2-3-4 for the consoles).

Right I understand that...but if were to put the -smp switch on the gui client would it have any effect?

 

[Kendrak]

is there a way to have the gui client run on more than one core? I really like the visualizations

They are nice to look at, however they slow down the prosses by a noticable amount. If you are going through the troubble of getting all of your cores going, why give back a large amount of gain? ( my understanding is about a 10 precent hit.)

 

[nitrobass24]

hmm ok thats a good point i didnt think about.

 

[Xilikon]

Right I understand that...but if were to put the -smp switch on the gui client would it have any effect?

The GUI client have no SMP support, only the 6.22 SMP console client is available.

You could also have something as hybrid like this : 1 GUI client on 1 core and 3 SMP clients to soak the 7 other cores. You retain the vizualisation candy and you get the performance out of all cores. However, it's a bit complicated to do (I have a guide which should be available very soon on the official F@H side that I wrote today).

 

[nitrobass24]

The GUI client have no SMP support, only the 6.22 SMP console client is available.

You could also have something as hybrid like this : 1 GUI client on 1 core and 3 SMP clients to soak the 7 other cores. You retain the vizualisation candy and you get the performance out of all cores. However, it's a bit complicated to do (I have a guide which should be available very soon on the official F@H side that I wrote today).

Well right now I have 1 GPU Client running, 1 CPU Gui client running, 1 smp console running.

 

[Xilikon]

Well right now I have 1 GPU Client running, 1 CPU Gui client running, 1 smp console running.

Ok, with that combination, you could add a second SMP client and you will be good to go. Just make sure the GPU client is set so the priority is slighty higher to grab the cycles it need and leave the rest.

 

[nitrobass24]

Just make sure the GPU client is set so the priority is slighty higher to grab the cycles it need and leave the rest.

How would I do that? you mean like the process priority that windows sets?

 

[Xilikon]

How would I do that? you mean like the process priority that windows sets?

Enter the GPU client configuration window, select the 3rd tab and you will see a option to set the priority on the upper part of this tab.