• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question about Folding with Dual Core

Trikat

Diamond Member
Is it possible to have the F@H program utilize both cores at 100%?
If it is possible to have it utilize both cores at 100% is there a way to throttle it to use only 90%?

I know that I can run 2 instances of F@H by "installing" it twice (thus 100% CPU load), but is there a way to throttle it to use only 90%?
 
You'll need to use 2 instances. Use the non-GUI version. When you are setting it up, it will ask you what % of the CPU you want to allocate. Set each of them to 95%. This will leave 5% of each core idle, or together 10%.
 
Use the cli and create two folders, say CPU1 and CPU2. Setup a client in each of them. The only thing that needs to be different is the machineid when asked during the setup, make one 1 and one 2 like so machineid=1 for the folder CPU1 and for folder CPU2 machineid=2. As Folding will run at idle priority you can set both the CPU usage to 100% Anything else that will need cpu power will take it away from f@h.

You can also have a look at MDE's awesome F@H setup guide here. 😀
 
Oops another question. I wanted to run the grahpical version, because it is easier to setup. Would I beable to do that with dual cores? (Install 2 instances of the graphic version and set the affinities) Or will the WUs conflcit etc.
 
I'm not positive on this, but i believe you can't run 2 instances of the graphical version. 1 graphical & 1 CLI possibly though.
 
You can run one GUI and one CLI.

The reason you cannot run two GUI is that you cannot set MachineID in the GUI, it defaults to 1.

It is important to have the second client set to MachineID 2 - actually any number 2-8.

Also, you must add to the CLI startup shortcut the switch "-local" (without the quotes), once you are in there might as well add the "-forceasm" flag too.
 
Back
Top