High-Memory Queues
Details on Jobs that Produced a Warning
As of Wed Apr 15 04:07:06 EDT 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
13143855.1 diamond_coconet bourkeb mThM.q - 800.0G > 742.926G - 29.811G 32.724G 16.6d 1.7d 62.8% 16/mthread
13143856.1 diamond_coconet bourkeb mThM.q - 800.0G > 766.492G - 29.780G 32.669G 12.7d 1.7d 47.8% 16/mthread
13160862.1 assemble-spades lealc mThM.q - 200.0G >> 97.674G - 23.085G 15.220G 6.1d 10.9h 83.9% 16/mthread
12854032.1 montagem-longin santossam mThM.q - 120.0G >> 35.599G - 0.517G 2.196G 7.2d 6.7d 5.4% 20/mthread
12190422.1 stairwayAZ.job byerlyp lThM.q - 20.0G >> 3.408G - 3.408G 3.375G 57.7d 57.8d 20.0% 5/mthread
13144017.1 QTreeGala133_04 castanedaric lThM.q - 200.0G >> 46.032G - 45.965G 36.260G 30.2d 1.4d 85.0% 25/mthread
13143907.1 raxml_hmem coellogarrid lThM.q - 120.0G >> 3.616G - 3.587G 3.569G 63.8d 1.6d 99.5% 40/mthread
13144088.1 run_apr14_2026_ szieba lThM.q - 1.0G << 1.027T - 225.910G 3.765G 11.6d 1.0d 18.6% 60/mthread
13144087.1 run_apr14_2026_ szieba lThM.q - 1.0G << 963.497G - 13.417G 3.324G 12.1d 1.0d 19.3% 60/mthread
12827067.1 spades cabreroa lThM.q - 0.0G << 248.409G - 11.168G 39.003G 60.0d 7.5d 80.0% 10/mthread
12795448.1 IQ_phy_cerrado nevesk lThM.q - 200.0G >> 73.070G - 16.001G 15.969G 484.7d 16.3d 98.9% 30/mthread
12195552.1 stairwayNE.job byerlyp lThM.q - 20.0G >> 3.472G - 3.472G 3.434G 57.4d 57.6d 19.9% 5/mthread
13160152.1 Josa20 martinezl2 lThM.q - 50.0G >> 30.590G - 30.590G 30.561G 5.0d 12.8h 234.0% 4/mthread
12198833.1 stairwayCAR.job byerlyp lThM.q - 20.0G >> 3.472G - 3.472G 3.434G 56.3d 56.7d 19.8% 5/mthread
12805305.1 raxmlHPC-PTHREA castanedaric lThM.q - 12.0G << 20.231G - 19.626G 18.717G 139.9d 11.7d 99.6% 12/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
Wednesday, 15-Apr-2026 04:11:12 EDT
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|