Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The first WU downloaded will use only ONE CPU. #1261

Open
bb30994 opened this issue Dec 19, 2018 · 2 comments
Open

The first WU downloaded will use only ONE CPU. #1261

bb30994 opened this issue Dec 19, 2018 · 2 comments
Labels
3.Component - FAHClient Reported issue relates to FAHClient.

Comments

@bb30994
Copy link

bb30994 commented Dec 19, 2018

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.

@shorttack shorttack added the 3.Component - FAHClient Reported issue relates to FAHClient. label Apr 14, 2020
@shorttack
Copy link

@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?

@bb30994
Copy link
Author

bb30994 commented Apr 21, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.Component - FAHClient Reported issue relates to FAHClient.
Projects
None yet
Development

No branches or pull requests

2 participants