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
On a new installation of FAHClient the first WU will never use more than one CPU. After that WU is completed, future WUs will use SMP in accordance with the configuration setting.
Strictly guessing here: a new FAHClient runs with a default value of either or ...v='1'/> or maybe with ...v='-1'. but GROMACS corrects it to be 1. For subsequent WUs config.xml is consulted.
The text was updated successfully, but these errors were encountered:
@bb30994 Is this still an issue? I added a CPU and it picked up the appropriate number of cores on Windows and Linux (while GPU continued. I did not try a scratch install). Should this case be closed or fixed?
This is still an issue, but I've discovered more information. I believe this is true simply because the first WU is downloaded before the default number of CPUs is calculated. See #1410.
If, for a new installation, the initial value of CPU threads is set to 1 and a WU is downloaded before a new value is chosedn by the configuration step, then that WU must be finished with no more that 1 thread. Assigning a larger number of threads will not change the internal restriction that the WU acquired when it was downloaded.
This isn't quite a duplicate of #1410 but rather a special case of it. If the client calculates the preferred value (like a setting of -1) before the WU is downloaded, this ticket can be closed whether or not #1410 is resolved.
On a new installation of FAHClient the first WU will never use more than one CPU. After that WU is completed, future WUs will use SMP in accordance with the configuration setting.
Strictly guessing here: a new FAHClient runs with a default value of either or ...v='1'/> or maybe with ...v='-1'. but GROMACS corrects it to be 1. For subsequent WUs config.xml is consulted.
The text was updated successfully, but these errors were encountered: