Before you start#
Requested resources and resources actually used are different. sacct reports recorded fields; seff summarizes efficiency for the same job. Use this table as a lookup while reading the output, rather than memorizing six definitions.
| Resource | Reservation | Observation to compare |
|---|---|---|
| CPU | AllocCPUS | CPU efficiency in seff; allocated does not mean used |
| Memory | ReqMem, with its units and per-CPU/total meaning | MaxRSS on the relevant job step |
| Time | Requested maximum time | Elapsed, the actual run time |
State and ExitCode say how the job ended. Inspect a software failure before changing its resources. The tiny training job helps locate these fields; only a representative workload can support a production sizing decision.
A serial run reserved four CPUs, 16 GiB per CPU and two hours, but took 20 minutes with 22% CPU efficiency and 9 GiB MaxRSS. Before reading the model, which reservations look unsupported by this evidence? The official questions ask you to choose the next test for this fictional case.
Reason about the next test
Four times 16 GiB reserves 64 GiB. If the program is serial, more allocated CPUs do not make its computation parallel. Compare memory and time with the observed values, leave sensible headroom, and test the reduced request on representative input. One sample does not establish every production input's needs. An import error needs a software fix, not an unexplained increase in resources.
Treating a deliberately tiny calculation as a production benchmark, or increasing every resource after an error without diagnosing it.