High-Memory Queues
Details on Jobs that Produced a Warning
As of Sun Mar 15 06:07:08 EDT 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
12248637.1 sansibia_spades nelsonjo mThM.q - 420.0G >> 12.402G - 7.862G 7.322G 15.2d 11.6d 13.1% 10/mthread
12759684.1 angsd2_arg.job beckerm mThM.q - 80.0G >> 18.802G - 16.007G 11.482G 1.9d 20.1h 28.9% 8/mthread
12759565.1 angsd2_arg.job beckerm mThM.q - 80.0G >> 40.311G - 21.014G 15.010G 3.8d 1.7d 28.6% 8/mthread
12190422.1 stairwayAZ.job byerlyp lThM.q - 20.0G >> 3.408G - 3.408G 3.369G 26.8d 26.9d 19.9% 5/mthread
12195552.1 stairwayNE.job byerlyp lThM.q - 20.0G >> 3.472G - 3.472G 3.422G 26.6d 26.7d 19.9% 5/mthread
12586423.1 treemix_batch uribeje lThM.q - 600.0G >> 16.266G - 16.197G 16.175G 3.6d 3.6d 5.0% 20/mthread
12198833.1 stairwayCAR.job byerlyp lThM.q - 20.0G >> 3.472G - 3.472G 3.421G 25.5d 25.8d 19.7% 5/mthread
12647567.1 treemix_batch uribeje lThM.q - 600.0G >> 9.088G - 9.088G 9.069G 2.9d 2.9d 5.0% 20/mthread
|
A warning is generated if either:
• too much or too little memory is reserved:
mem_res versus max(vmem); or
• the job efficiency is too low or is too high.
Click on the link under the jobID.tID
heading to view the job's corresponding graph.
The quantity
mem_res is the amount of memory reserved for the job, while
max(vmem) is the maximum amount of memory a job has used (so far);
to optimize the cluster's memory usage, these two numbers should be similar.
The job efficiency, eff., is the amount of CPU used so far divided by the product of the
age by the number of slots.
• A low efficiency means that the job is not using all the allocated CPUs (slots);
• a value above 100% means that the job is using more CPUs cycles
(threads) than the requested number of slots (nslots).
|
This page was last updated on
Sunday, 15-Mar-2026 06:11:15 EDT
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|