Folding Forum

Flathead74 wrote:Works ok, here.

rilian wrote:Works good at crunchers from my team with following:

2хSMP + ACh + 2xGPU clients

...

C2Quad Q6600 (3600МГц) / MEM 2x1024 GoodRam DDRII 900 (1125МГц) / Abit IP35 Pro / 2xWinSMP (ACh) +
GF 8800GTS 512MB (761/1902/2000) + GF 9600GSO 384MB (700/1901/1600)

gives around 14000 PPD

[settings]
username=Vorchun
team=2164
passkey=хххххххххххххххххххххххххххххххх
asknet=no
machineid=3
bigpackets=big
extra_parms=-gpu 0
local=

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

[core]
priority=100
cpuusage=100
disableassembly=no
nocpulock=0
checkpoint=30
ignoredeadlines=yes

[power]
battery=no

[clienttype]
memory=1024
type=3

Optimal params for Quad and two GPU

2GPU, 2SMP, ACh
Do not create NV_FAH_CPU_AFFINITY in registry, core of GPU1 assigns itself to CPU_core_4, core of GPU2 assigns itself to CPU_core_3. PPD for SPM drops on 12-15% (!)

GPU params: priority=100, cpuusage=100

===========
For Core Duo and one GPU (C2D E8200 + 8800GT) - 1GPU client and 1 SMP client

Create NV_FAH_CPU_AFFINITY = 0 so FahCore_11.exe will assign to both CPU cores. Use ACh
In this case GPU_PPD = 4400, SMP_PPD=1900 (Cpu at 3000MHz)

britgeezer wrote:Now I'm also running GPU2 and need to consider core (3) should be dedicated to GPU2, I'm disappointed with output on SMP CPU with 6.22 beta running 1x SMP and in fact found that limiting the SMP to cores 0 & 1 increased output.

gwildperson wrote:

britgeezer wrote:Now I'm also running GPU2 and need to consider core (3) should be dedicated to GPU2, I'm disappointed with output on SMP CPU with 6.22 beta running 1x SMP and in fact found that limiting the SMP to cores 0 & 1 increased output.

Did you actually measure this? With nothing except one 6.22beta client running, what are the frame times if you manually set all four fahcore_a1's to
* Cores 0 and 1
* Cores 0 1 and 2
* Cores 0 1 2 and 3

From what I read, fahcore_a1 doesn't scale very well and will soon be replaced by fahcore_a2 so I'm not sure of the long-term value of these measurments. In any case, I find it hard to believe that the first one is faster than the third, but don't have any solid information.

Maybe by "increased output" are you also considering other clients are doing simultaneously. I have no doubt that the third one is less that twice as fast as the first one. Because of that, two clients (cores 0,1 and cores 2,3) does more work than just one of them, which is what "does not scale well" means.

rilian wrote:will this help?

from our forum

http://distributed.org.ua/forum/index.p ... entry29222

Code: Select all

[settings]
username=Vorchun
team=2164
passkey=хххххххххххххххххххххххххххххххх
asknet=no
machineid=3
bigpackets=big
extra_parms=-gpu 0
local=

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

[core]
priority=100
cpuusage=100
disableassembly=no
nocpulock=0
checkpoint=30
ignoredeadlines=yes

[power]
battery=no

[clienttype]
memory=1024
type=3

Another one:
http://distributed.org.ua/forum/index.p ... entry27856

Optimal params for Quad and two GPU

2GPU, 2SMP, ACh
Do not create NV_FAH_CPU_AFFINITY in registry, core of GPU1 assigns itself to CPU_core_4, core of GPU2 assigns itself to CPU_core_3. PPD for SPM drops on 12-15% (!)

GPU params: priority=100, cpuusage=100

===========
For Core Duo and one GPU (C2D E8200 + 8800GT) - 1GPU client and 1 SMP client

Create NV_FAH_CPU_AFFINITY = 0 so FahCore_11.exe will assign to both CPU cores. Use ACh
In this case GPU_PPD = 4400, SMP_PPD=1900 (Cpu at 3000MHz)

rilian wrote:Note, Fah SMP 6.22 has only one PROCESS with 4 threads, while early versions (5.91) run 4 PROCESSES each with one thread. Process may be assigned to some core, thread - no (at least by outer program). That is why using affinity changer does not make sense and you do not get additional 10% speedup.

i also do not know whether this new fah client assign affinities correctly (i would guess "no")