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

Create resource group to apply memory setting for Isambard Instinct #282

Merged
merged 4 commits into from
Mar 18, 2024

Conversation

giordano
Copy link
Member

@kaanolgu can you please check this works for you? If I remember correctly, we need to define the extra_resource so that it's applied in the configuration, but in this case we don't need (yet?) to define any custom variable, so I think an empty dictionary should work?

@giordano giordano requested a review from kaanolgu March 13, 2024 15:07
benchmarks/modules/utils.py Outdated Show resolved Hide resolved
benchmarks/modules/utils.py Outdated Show resolved Hide resolved
benchmarks/modules/utils.py Outdated Show resolved Hide resolved
benchmarks/reframe_config.py Outdated Show resolved Hide resolved
benchmarks/modules/utils.py Outdated Show resolved Hide resolved
@giordano
Copy link
Member Author

The reason why we haven't dealt with the memory as a proper resource so far is because it's complicated: it's a mixture of application-specific (memory requirements can vary a lot) and system-specific (I think for some schedulers it's the memory per CPU, in others it's the total memory), so it's really hard to come up with reasonable default values which work well in all situations.

@giordano
Copy link
Member Author

@kaanolgu is it good to go now?

@kaanolgu
Copy link
Contributor

@kaanolgu is it good to go now?

LGTM

@giordano giordano merged commit d1c413e into main Mar 18, 2024
4 checks passed
@giordano giordano deleted the mg/instinct-memory branch March 18, 2024 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants