High-Memory Queues
Details on Jobs that Produced a Warning
As of Sun Feb 15 11:47:05 EST 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
11857696.1 Step8_Diamond_5 bourkeb mThM.q - 256.0G >> 72.881G - 30.767G 31.153G 29.3d 2.7d 66.7% 16/mthread
11857705.1 Step8_Diamond bourkeb mThM.q - 256.0G >> 72.719G - 29.797G 30.960G 20.3d 2.7d 46.3% 16/mthread
12104874.1 Vitis_Prune_Dis niez mThM.q - 400.0G << 530.477G - 479.564G 302.050G 11.9h 8.8h 4.2% 32/mthread
11812791.1 stairway.job byerlyp lThM.q - 100.0G >> 3.472G - 3.472G 3.391G 10.9d 11.0d 5.0% 20/mthread
11801118.1 angsd_strict uribeje uThM.q - 200.0G >> 153.028G - 152.350G 106.742G 28.5d 26.8d 13.3% 8/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-Feb-2026 11:51:12 EST
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|