If you are running windows, could be that the windows version does not support more than 32 threads on a single task.
Best to use the most current version of the FAH software.
You might check your fah logs to verify how many threads are being used by each wu. Possible that limited supply of projects available for 32 threads, the assigned wu are using less threads, and there might be some other optimum for slot config.
I do not have any hardware with more than 12 threads, but setting cpu 7 on fah v7.5.1 results in the software changing to non-prime cpu 6. Example in FAH log below, the CPU 7 set in the config is displayed as "-np 7" and software auto-changed to 6 threads. In case you are wondering why/how a cpu slot would be setup with 7 threads. A quad core cpu with HT enabled has 8 threads and a default FAH install on a host with one GPU will set up a CPU slot with n-1 threads (7), which may not have any valid assignments. However, the v7.5.1 FAH software is able to auto-negotiate with the assignment server until a workable thread count is reached for available project. The older versions of the FAH software are not able to negotiate thread count and the slot will remain idle, if no project meets the request.
Best to use the most current version of the FAH software.
You might check your fah logs to verify how many threads are being used by each wu. Possible that limited supply of projects available for 32 threads, the assigned wu are using less threads, and there might be some other optimum for slot config.
I do not have any hardware with more than 12 threads, but setting cpu 7 on fah v7.5.1 results in the software changing to non-prime cpu 6. Example in FAH log below, the CPU 7 set in the config is displayed as "-np 7" and software auto-changed to 6 threads. In case you are wondering why/how a cpu slot would be setup with 7 threads. A quad core cpu with HT enabled has 8 threads and a default FAH install on a host with one GPU will set up a CPU slot with n-1 threads (7), which may not have any valid assignments. However, the v7.5.1 FAH software is able to auto-negotiate with the assignment server until a workable thread count is reached for available project. The older versions of the FAH software are not able to negotiate thread count and the slot will remain idle, if no project meets the request.
Code:
01:41:34:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/v7/lin/64bit/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 705 -lifeline 1947 -checkpoint 4 -np 7
01:41:34:WU00:FS00:Started FahCore on PID 16462
01:41:34:WU00:FS00:Core PID:16466
01:41:34:WU00:FS00:FahCore 0xa7 started
01:41:35:WU00:FS00:0xa7:Digital signatures verified
01:41:35:WU00:FS00:0xa7:Reducing thread count from 7 to 6 to avoid domain decomposition by a prime number > 3
01:41:35:WU00:FS00:0xa7:Calling: mdrun -s frame11.tpr -o frame11.trr -cpi state.cpt -cpt 4 -nt 6
01:41:35:WU00:FS00:0xa7:Steps: first=5500000 total=500000
01:41:36:WU00:FS00:0xa7:Completed 53092 out of 500000 steps (10%)
