Ticket 20598 - sacct: support memory allocation for step
Summary: sacct: support memory allocation for step
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Accounting (show other tickets)
Version: 24.05.1
Hardware: Linux Linux
: 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2024-08-02 13:21 MDT by Yaroslav Nikitenko
Modified: 2024-08-02 13:21 MDT (History)
0 users

See Also:
Site: -Other-
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Yaroslav Nikitenko 2024-08-02 13:21:54 MDT 
In the manual of sacct there is a formatting field

ReqMem    Minimum required memory for the job...  Note: This value is only from the job allocation, not the step.

It would be good if that were possible to output that value for each job step.

Rationale: there is a big confusion among users what memory limitations are being transferred to job steps from the created job (which, in turn, affects productivity). It would be useful to see the real values.