A couple of notes on adding Folding@Home to the fray ...
Folding@Home is biased towards GPU and Rosetta@Home is biased toward CPU workloads. F@H is pretty disorganized and I found their local management tools to be less mature, but they also do good work. F@H is also having trouble keeping up with supply — there is plenty to work on, but their servers can't dish it out fast enough and so machines end up idling a lot.
So what I've done is install both and used some of the config in both facilities to share the time. Basically, if F@H has workload, I bias towards that and otherwise run R@H. I created an F@H Bimmerpost team as well (team number: 243241), but my primary F@H contributions have been a different team (work-related), so I have almost nothing on Bimmerpost F@H as of this note. It is still also a great cause, however.
Something to consider doing. Basically, if you want to contribute and simplicity, just do Rosetta@Home. If you are willing to play with configs and, in particular have lots of GPU resources to contribute, do Folding@Home and/or both and config to share time appropriately.
__________________
G05 X5 x40i (04/2019 mfg, Canada) on S18A-19-11-540
|