High-Memory Queues
Details on Jobs that Produced a Warning
As of Thu Feb 19 10:17:06 EST 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
12198995.10 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.557G - 23.362G 23.286G 3.6d 1.9d 96.1% 2/mthread
12198995.11 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.659G - 23.553G 23.475G 4.5d 1.7d 135.1% 2/mthread
12198995.12 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.747G - 23.578G 23.505G 3.4d 1.6d 107.5% 2/mthread
12198995.14 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.742G - 23.582G 23.501G 3.6d 1.6d 115.8% 2/mthread
12198995.16 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.759G - 23.585G 23.496G 3.4d 1.5d 113.6% 2/mthread
12198995.22 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.771G - 23.588G 23.513G 31.3h 17.6h 88.7% 2/mthread
12198995.23 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.905G - 23.714G 23.641G 31.0h 13.2h 117.7% 2/mthread
12198995.24 euk-SNP_array johnsonsj mThM.q - 40.0G >> 23.397G - 23.335G 23.261G 21.6h 10.7h 100.8% 2/mthread
12201321.1 final_ASC campanam mThM.q - 400.0G >> 11.961G - 11.815G 11.070G 31.6d 17.4h 90.7% 48/mthread
12201322.1 final_ASC campanam mThM.q - 400.0G >> 10.177G - 7.060G 9.447G 30.9d 17.4h 88.9% 48/mthread
12190422.1 stairwayAZ.job byerlyp lThM.q - 20.0G >> 3.345G - 3.345G 3.313G 3.0d 3.0d 20.0% 5/mthread
12195552.1 stairwayNE.job byerlyp lThM.q - 20.0G >> 3.345G - 3.345G 3.313G 2.9d 2.9d 20.0% 5/mthread
12198833.1 stairwayCAR.job byerlyp lThM.q - 20.0G >> 3.345G - 3.345G 3.311G 2.0d 2.0d 19.9% 5/mthread
12198654.1 xangsd_strict uribeje uThM.q - 200.0G >> 19.732G - 19.656G 14.304G 14.1d 2.7d 65.0% 8/mthread
12199275.1 xPSMC4 uribeje uThM.q - 400.0G >> 0.735G - 0.337G 0.488G 30.3h 1.3d 12.5% 8/mthread
11801118.1 angsd_strict uribeje uThM.q - 200.0G > 165.493G - 165.038G 112.882G 32.5d 30.7d 13.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
Thursday, 19-Feb-2026 10:21:18 EST
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|