Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
mem-per-gpu
See original GitHub issueI want to use --mem-per-gpu which I can set using the addtional-parameters, but since it is incompatible with the --mem flag, it causes sbatch to crash since --mem is set automatically. Can --mem be made optional?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Generic Resource (GRES) Scheduling
Define how tasks are bound to GPUs. --gpu-freq: Specify GPU frequency and/or GPU memory frequency. --mem-per-gpu: Memory allocated per GPU.
Read more >[slurm-users] Strange memory limit behavior with --mem-per-gpu
I have a user who submitted an interactive srun job using: srun --mem-per-gpu 64 --gpus 1 --nodes 1 .... From sacct for this...
Read more >Using GPUs with Slurm - CC Doc
There are a variety of other directives that you can use to request GPU resources: --gpus, --gpus-per-socket, --gpus-per-task, --mem-per-gpu ...
Read more >GPU Jobs - High Performance Computing
This page explains how to submit GPU jobs to the Discovery Cluster using Slurm. Partitions with GPUs. Below is the list of partitions...
Read more >GPU nodes - Stanford Sherlock cluster
--mem-per-gpu : allocates (host) memory per allocated GPU . Other options can help set particular GPU properties (topology, frequency...): --gpu ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, I think this is a good idea to add
mem_per_gpuand removingProviding a default mem is probably not a good anyway, we should use the cluster default (which is not setting anything).
A PR would be welcome, you’d be the first external contributor 😃
But if I may ask, why is your scheduling GPU centered ? For me it makes more sense to have a task centered scheduling, and I typically have one task per gpu.
Solved by #22