FAH provides a V7 client installer for Debian / Mint / Ubuntu / RedHat / CentOS / Fedora. Installation on other distros may or may not be easy but if you can offer help to others, they would appreciate it.
Have been using cputhrottle - to keep the system under 50 C - but it tends to freeze after several days... so i looked for another solution. It seems that there is a cpulimit program, which we also have installed.
When i run htop i see at least 8 processes that have "fah" in them. Does anyone know how i should go about using cpulimit? i can't see trying to use it with each of the 8 or more PIDs i'm seeing under htop. Maybe it can be used just after the FAH program is run???
Have a beautiful week and be happy!
Last edited by frazelle09 on Tue Feb 25, 2025 3:05 am, edited 1 time in total.
"The earth is one country and mankind its citizens." Bahá'u'lláh "La tierra es un sólo país y la humanidad sus ciudadanos."
The actual processing is done in the FAHCore_nn processes, fah-client handles getting and returning WUs and processing the log files. The "nn" would be replaced with the core number, a8 and a9 for current CPU WUs and I am not certain the oldest GPU core still being used, but in the 20s.
frazelle09 wrote: ↑Tue Feb 25, 2025 1:43 am
Have been using cputhrottle - to keep the system under 50 C - but it tends to freeze after several days... so i looked for another solution. It seems that there is a cpulimit program, which we also have installed.
When i run htop i see at least 8 processes that have "fah" in them. Does anyone know how i should go about using cpulimit? i can't see trying to use it with each of the 8 or more PIDs i'm seeing under htop. Maybe it can be used just after the FAH program is run???
Have a beautiful week and be happy!
[tuto] openSUSE >= 15.3,Tumbleweed,How to get a silent and cold PC ?
How to add these statements to fah systemd service file ?
Thanks
I don't know enough about systemd for that. But it's preferable to have fewer fast cores than more slow cores. The only time you would want to limit the CPU usage itself is if for some reason you didn't want to just decrease the number of used cores.
But cgroups cpu.max is basically the same as cpulimit except it is handled by the kernel scheduler so it is much faster (turning the thread "on" and "off" much faster than cpulimit ever could). Here is a way to test it manually to see if it's what you want (this makes no persistent changes to your system and will not affect folding stability or reliability, but it will slow it down):
Then pause and unpause the core and the CPU usage should be limited to 50% (1000us of usage allowed in any given 2000us period). If you remove the /sys/fs/cgroups/fah directory, reboot, or restart the fah-client process itself, then the change will be undone.
But you should really try just folding on fewer cores instead like muziqaz suggested. That will be more efficient.
That too. If the machine is being loud (and isn't aging) then it's not designed to be silent under load. FAH puts the system under load and the more load, the better. Of course folding on that machine is better than nothing but you really shouldn't need to throttle its usage.
There used to be a way to directly pass extra arguments to the core, and you could pass -cpu and then a percentage. This is no longer possible with the v8 client although the core still supports it. I read on github that there were no plans to restore the ability to pass extra arguments to the core.
That ability to pass "-cpu" to the core dates back to very old single threaded CPU folding cores. The last I knew it did not work properly with newer multi-threaded cores, it just limited one thread. Indirectly that slowed things down as the other threads all would be waiting for the slowed thread to catch up.
The rest of the uses of passing parameters to the folding cores in the v7 client were mostly used for testing purposes, not in general usage.