The easiest way to check the instantaneous memory and CPU usage of a job is to ssh to a compute node your job is running on.
If your job is already running, you can check on its usage, but will have to wait until it has finished to find the maximum memory and CPU used. To know how much RAM your job used (and what jobs like it will need in the future), look at the "Maximum resident set size" Running Jobs Stress-ng: info: successful run completed in 10.08sĬommand being timed: "stress-ng -cpu 8 -timeout 10s" User time (seconds ): 80.22Įlapsed (wall clock ) time (h:mm:ss or m:ss ): 0:10.09Īverage shared text size (kbytes ): 0 Average unshared data size (kbytes ): 0 Average stack size (kbytes ): 0 Average total size (kbytes ): 0 Maximum resident set size (kbytes ): 6328 Average resident set size (kbytes ): 0 Major (requiring I/O ) page faults: 0 Minor (reclaiming a frame ) page faults: 30799 Voluntary context switches: 1380 Involuntary context switches: 68 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0
National ~ ]$ /usr/bin/time -v stress-ng -cpu 8 -timeout 10s
0 kommentar(er)
