High-Memory Queues
Details on Jobs that Produced a Warning
As of Thu Jul 30 10:07:11 EDT 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
15302488.1 blast parras sThM.q - 900.0G >> 487.315G - 487.315G 252.974G 13.8h 0.9h 50.1% 30/mthread
15302149.1 assemble-spades lealc mThM.q - 200.0G >> 127.866G - 0.702G 16.895G 9.9d 18.6h 79.4% 16/mthread
15298719.1 mf_trm2 wirshingh mThM.q - 72.0G > 68.102G - 3.035G 2.925G 10.4d 2.9d 39.3% 9/mthread
15301656.1 earlgrey zhangy lThM.q - 192.0G >> 29.135G - 0.696G 1.565G 5.7d 1.1d 43.0% 12/mthread
15301656.2 earlgrey zhangy lThM.q - 192.0G >> 7.794G - 3.532G 1.561G 8.8d 1.1d 66.9% 12/mthread
15301656.3 earlgrey zhangy lThM.q - 192.0G >> 43.915G - 2.545G 1.143G 11.0d 1.1d 83.9% 12/mthread
15301656.5 earlgrey zhangy lThM.q - 192.0G >> 8.165G - 2.709G 1.623G 9.3d 1.1d 70.9% 12/mthread
15301656.6 earlgrey zhangy lThM.q - 192.0G >> 9.698G - 4.014G 1.579G 9.2d 1.1d 70.0% 12/mthread
15301646.1 ROST_angsd byerlyp lThM.q - 150.0G >> 82.472G - 82.472G 20.200G 1.8d 1.2d 15.0% 10/mthread
15293594.1 raxml_hmem athalappila lThM.q - 120.0G >> 71.743G - 71.743G 70.786G 268.6d 6.8d 98.6% 40/mthread
15300160.9 imaging_array jmichail uThM.q - 70.0G >> 53.319G - 51.510G 46.757G 22.7h 18.0h 126.4% 1
15300160.12 imaging_array jmichail uThM.q - 70.0G > 65.919G - 62.304G 52.428G 23.3h 5.6h 420.4% 1
15300160.13 imaging_array jmichail uThM.q - 70.0G > 59.855G - 58.238G 44.401G 15.5h 1.9h 815.1% 1
15300040.1 Hifi_P2_HICdata gonzalezv uTxlM.rq - 1.758T >> 31.174G - 10.299G 11.052G 19.5d 1.6d 13.2% 90/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, 30-Jul-2026 10:11:59 EDT
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|