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

Forkhead #654

Merged
merged 5 commits into from
Oct 14, 2022
Merged

Forkhead #654

merged 5 commits into from
Oct 14, 2022

Conversation

scimerman
Copy link
Contributor

No description provided.

slurm_max_cpus_per_node: "{{ slurm_sockets * slurm_cores_per_socket - 8 }}"
slurm_max_mem_per_node: "{{ slurm_real_memory - 8 * 2048 }}"
slurm_max_cpus_per_node: "{{ slurm_sockets * slurm_cores_per_socket - 2 }}"
slurm_max_mem_per_node: "{{ slurm_real_memory - 8 * 512 }}"
Copy link
Contributor

@pneerincx pneerincx Oct 14, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When the amount of RAM, we want to reserve for the OS and everything else that is not a Slurm job, does not depend on the amount of cores, it does not make sense to multiply values here. Instead of
slurm_max_mem_per_node: "{{ slurm_real_memory - 8 * 512 }}"
you can just use:
slurm_max_mem_per_node: "{{ slurm_real_memory - 4096 }}"
That will fail though on a small VM, which only has 4096 GB RAM in total.
slurm_max_mem_per_node: "{{ slurm_real_memory - slurm_sockets * slurm_cores_per_socket * 512 }}"
is a more flexible setup.

@scimerman scimerman requested a review from pneerincx October 14, 2022 09:50
@pneerincx pneerincx merged commit 9e2d698 into rug-cit-hpc:develop Oct 14, 2022
@scimerman scimerman deleted the forkhead branch October 14, 2022 13:24
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