User Tools

Site Tools


memory_reservation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
memory_reservation [2017/07/09 15:34]
meesters
memory_reservation [2017/08/20 17:48]
meesters
Line 10: Line 10:
  
 <code shell> <code shell>
-$ JobID%20,​ReqMem,​MaxRSS,​AveRSS,​Elapsed,​CPUTime -j JOBID+sacct -o JobID%20,​ReqMem,​MaxRSS,​AveRSS,​Elapsed,​CPUTime -j <JOBID>
 </​code>​ </​code>​
 where JOBID is the one you’re interested in. This sample command gives the output for all JobSteps and compares used CPU time with the actual elapsed time - sometimes useful to get performance hints. If your job completed long in the past you may have to tell ''​sacct''​ to look further back in time by adding a start time with -S YYYY-MM-DD. Note that for parallel jobs spanning multiple nodes, this is the maximum memory used on any one node; if you’re not setting an even distribution of tasks per node (e.g. with ''​%%--%%ntasks-per-node''​),​ the same job could have very different values when run at different times. where JOBID is the one you’re interested in. This sample command gives the output for all JobSteps and compares used CPU time with the actual elapsed time - sometimes useful to get performance hints. If your job completed long in the past you may have to tell ''​sacct''​ to look further back in time by adding a start time with -S YYYY-MM-DD. Note that for parallel jobs spanning multiple nodes, this is the maximum memory used on any one node; if you’re not setting an even distribution of tasks per node (e.g. with ''​%%--%%ntasks-per-node''​),​ the same job could have very different values when run at different times.
memory_reservation.txt · Last modified: 2018/06/27 10:12 by henkela