Community driven support forum for Folding@home
https://foldingforum.org/
Well, you can, but that requires programming in Wait states or other non-productive code. But basically F@h falls into the "compute-bound" type of process, it has calculations always ready to be done with limited amounts of other types of processing that would cause it to wait on. The client is set to run it at the lowest priority, the OS scheduler will preempt processing F@h for higher priority process that run.ronnieross wrote:Seems to be an interesting point of view on Computer Science: you can't slow down a process because of it executes forever and ever at the maximum speed CPU (aside voltage and clock configuration) can run.
I've found an utility, called cpulimit, that does the "dirty job" (maybe adding wait states or so...)Joe_H wrote:
Well, you can, but that requires programming in Wait states or other non-productive code. But basically F@h falls into the "compute-bound" type of process, it has calculations always ready to be done with limited amounts of other types of processing that would cause it to wait on. The client is set to run it at the lowest priority, the OS scheduler will preempt processing F@h for higher priority process that run.
Efficiency goes down: time for finishing job is circa X 3 (depending on final parameter you set from the command line).gunnarre wrote:How does does the cpulimit command affect efficiency? If it causes a lopsided effect on folding speed, due to poor thread synchronizaion, then it might not be a good idea to use.