You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was mentioned before in previous versions. This client will go nowhere if there is no "slot"/per device control. Pause only works globally.
Whichever way you look at it, you have to add slots as a concept back. Sometimes it is more beneficial to run 2 CPU slots (with let's say 15 threads used) instead of one 30 thread one. Fahcores simply do not scale well past certain amount of threads. Forcing a user to waste their resources without option to split into smaller thread count slots is counter productive.
A user with 192 cores/ 384 threads might even crash the fahcore/WU as witnessed before with even smaller thread count CPUs. In an era of massive multicore CPUs we will cause more problems rather than solutions
The text was updated successfully, but these errors were encountered:
It seems like the 'Resource Groups' ability, like slots, gives you the granularity you are asking for now:
Resource Groups can be added with a forward slash with a name (or a space separated list like: /RG1 /RG2), in the setting's 'Peers' section:
Then, save the configuration settings, and there will be configuration settings for 'per Resource Group' controls that can be adjusted independently. Once setup, there will be independent Start and Pause buttons for each Resource Group
Updated instructions for FAH v8.3.1:
In the Settings for the machine:
Add a Resource Group with a forward slash with a name (or a space separated list like: /RG1 /RG2)
Select the Resource Group to edit the settings for it:
Then, save the configuration settings, and there will be configuration settings for 'per Resource Group' controls that can be adjusted independently. Once setup, there will be independent Start and Pause buttons for each Resource Group:
This was mentioned before in previous versions. This client will go nowhere if there is no "slot"/per device control. Pause only works globally.
Whichever way you look at it, you have to add slots as a concept back. Sometimes it is more beneficial to run 2 CPU slots (with let's say 15 threads used) instead of one 30 thread one. Fahcores simply do not scale well past certain amount of threads. Forcing a user to waste their resources without option to split into smaller thread count slots is counter productive.
A user with 192 cores/ 384 threads might even crash the fahcore/WU as witnessed before with even smaller thread count CPUs. In an era of massive multicore CPUs we will cause more problems rather than solutions
The text was updated successfully, but these errors were encountered: