[#14] Show GPU usage against what the job requested
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating the command that reports GPU jobs and its integration with SLURM accounting. Check how requested GPU memory is represented and which accounting fields provide peak memory and utilisation. Done means completed jobs, and running jobs when requested, show requested memory alongside peak memory and utilisation.
Written by the indexing model from the issue text.
Description
When a GPU job ends, and on request while it runs, users see their GPU usage next to what they asked for, e.g. requested 4 GiB of GPU memory, peaked at 21.5 GiB, utilisation 100%. GPU sharing isn't enforced, so today no one, user or admin, sees when a job goes over its share.
Approach. SLURM already records each job's peak GPU memory and utilisation in its accounting database. The command reads that back, so nothing new needs collecting.
- Dominant language
- Go
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from WATonomous/watcloud-cli
-
[#6] Remove the size argument from docker startPossibly taken @Ixe9230 claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WATonomous/watcloud-cli#15 · 1 comment · 1 assignee ·
-
[#13.2] slurm run: --batch modePossibly taken @GavinDPinto claimed this 6 days ago. Open
WATonomous/watcloud-cli#31 · 1 assignee ·
-
[#13.1] slurm run: interactive jobsPossibly taken @GavinDPinto claimed this 6 days ago. Open
WATonomous/watcloud-cli#30 · 1 assignee ·
-
Release watcloud-cli v1.5 and deploy it through infra-configPossibly taken @Ixe9230 claimed this 2 days ago. Opengood first issue
Difficulty 4/5 1-2 days Newbie friendliness 28/100
WATonomous/watcloud-cli#28 · 1 assignee ·
-
[#13] Add a command that builds the job requestPossibly taken @GavinDPinto claimed this 6 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
WATonomous/watcloud-cli#22 · 1 assignee ·
All issues in WATonomous/watcloud-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
SocialGouv/iterion#2369 ·
Maintainers usually reply within 1 day
-
area/ci bug priority/p3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation help wanted needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
hivecommons/hive#11606 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
gravitational/teleport#69869 ·
-
category:agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LanternOps/breeze#8493 ·
Maintainers usually reply within 1 day