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

Add details on how to specify memory and other settings #75

Open
avahoffman opened this issue Jan 16, 2024 · 2 comments
Open

Add details on how to specify memory and other settings #75

avahoffman opened this issue Jan 16, 2024 · 2 comments
Assignees

Comments

@avahoffman
Copy link
Contributor

avahoffman commented Jan 16, 2024

Check in with Michael about how to set memory higher? And resolve some other questions

@caalo
Copy link
Collaborator

caalo commented Jan 17, 2024

Had a nice chat with Michael about this today:

Indeed, the sbatch --mem option does not guarantee memory allocation, and SciComp recommends requesting cores as a proxy for memory allocation:

If you think your job will need more than 4GB of memory, request one CPU for every 4GB required.

Why does requesting more CPU help with allocating more memory?

FH Gizmo has class J nodes which each have 24 cores and 384GB of memory, and class K nodes which each have 36 cores and 768GB of memory. So, if you think you will need 100GB of memory for your job, by this rule of thumb you would request 25 cores. You would be assigned to a class K node, and you would occupy 25/36 cores on that node. On this node, other users can use the remaining 11 cores. You would share the 768GB of memory all together and hope that the other users don't take up more memory than you need: the more cores you occupy on a node, less users will compete for memory. It's an imprecise system and SciComp has interest to make memory allocation more precise in the future.

Note: on other SLURM systems, sbatch --mem does have implications about memory allocation.

@avahoffman
Copy link
Contributor Author

awesome recon, thank you!

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

No branches or pull requests

2 participants