Limit QWS RIKYU threads to scheduler cap - #95
Merged
Conversation
Signed-off-by: yoshifuminakamura <nakamura@riken.jp>
yoshifuminakamura
force-pushed
the
feature/rikyu-qws-cpu-cap
branch
from
August 7, 2026 09:40
5dae6d1 to
51314f5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reduce the QWS RIKYU run configuration from 36 OpenMP threads to 32 threads.
Reason
RIKYU now rejects jobs that request more than 32 CPUs per GPU. The current QWS RIKYU configuration requests one GPU with
--cpus-per-task=36, which fails at Slurm submission time.Validation
BK_ALLOCATION_PROJECT_ID=rkp00015 bash scripts/matrix_generate.sh--cpus-per-task=32 --gpus=1bash scripts/tests/test_scheduler_extra_args.shgit diff --check