High-Memory Queues
Details on Jobs that Produced a Warning
As of Fri Jan 23 15:17:05 EST 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
11801118.1 angsd_strict uribeje uThM.q - 200.0G >> 66.549G - 66.182G 43.114G 4.4d 3.9d 14.2% 8/mthread
11802867.1 Apr06_Cubing_mp jmichail uThM.q - 44.0G >> 10.296G - 9.953G 8.300G 1.8d 5.9h 93.2% 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
Friday, 23-Jan-2026 15:21:54 EST
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|