-
Notifications
You must be signed in to change notification settings - Fork 5
use standard limit for A64FX: only use quarter of available cores + fix determining level of parallelism in a way compatible with EasyBuild 4.x and 5.x #17
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
Conversation
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
New job on instance
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would have probably used set_maximum, 12
, but unlikely that this makes a difference for A64FX
. Will it work with EB 4.9.4?
@trz42 I went for the "divide by 4" approach because that effectively means we quadruple available memory, regardless of much cores are available. If we for some reason start requested partial nodes (say 12 cores rather than 48), we would be in trouble again. Should work file with EasyBuild 4.9.4 since there we still use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should also address EESSI/software-layer#1104 here, see boegel#1
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
New job on instance
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.