"This change both simplifies the setup of Folding@home and makes it possible for Folding@home to allocate multiple CPUs and GPUs to the same Work Unit. By allocating more resources to a single WU, Folding@home can decrease simulation times and achieve scientific results more quickly."
How do i get this to work? CPU and GPU working on 1 unit instead of 2 all the time???
This change both simplifies the setup of Folding@home and makes it possible for Folding@home to allocate multiple CPUs a
Moderators: Site Moderators, FAHC Science Team
-
Buick350X
- Posts: 11
- Joined: Sat Dec 13, 2025 3:38 pm
- Hardware configuration: Processor AMD Ryzen 9 5950X
MB AsRock B550M Pro4
RAM HP V6 DDR4 3000mhz 32.0 GB
Zotac Gforce 5060 TI 16GB TwinEdge OC - Contact:
Re: This change both simplifies the setup of Folding@home and makes it possible for Folding@home to allocate multiple CP
annoying when I want to use my PC, hit stop when finished, GPU always done fast, but then gotta wait n wait n wait for CPU to finish. why don't the GPU jump in and help?
-
Joe_H
- Site Admin
- Posts: 8330
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: This change both simplifies the setup of Folding@home and makes it possible for Folding@home to allocate multiple CP
The v8 series of clients includes support for a potential usage of both CPU and GPU on the same WU. Currently that is only a potential. The underlying software used in the folding cores supports it, but internal testing is needed to see how best to set it up for a varied group of hardware. Possible to set up for a fixed GPU and CPU pair, but early tests had mixed results on other hardware.
There are directions for setting up resource groups to process CPU and GPU projects separately on the same system. That will decouple getting new projects and no waiting for new WUs. As for pausing, CPU projects can be paused and will resume at almost the same place they were stopped. The GPU can't just "jump in" and help run it faster under the current settings.
There are directions for setting up resource groups to process CPU and GPU projects separately on the same system. That will decouple getting new projects and no waiting for new WUs. As for pausing, CPU projects can be paused and will resume at almost the same place they were stopped. The GPU can't just "jump in" and help run it faster under the current settings.