High-Memory Queues
Details on Jobs that Produced a Warning
As of Fri Jul 10 10:17:13 EDT 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
14966566.1 clNo_1000 peresph mThM.q - 20.0G >> 9.255G - 8.642G 8.579G 35.2d 3.5d 99.4% 10/mthread
14969201.1 mf_trimmedreads wirshingh mThM.q - 72.0G >> 34.389G - 1.832G 2.526G 6.1d 1.7d 40.2% 9/mthread
14966565.1 clcor1000 peresph mThM.q - 20.0G >> 8.641G - 8.641G 7.151G 35.2d 3.5d 99.5% 10/mthread
14969493.1 run_S5 szieba lThM.q - 1.0G << 139.611G - 139.611G 2.723G 52.4d 1.3d 80.0% 50/mthread
14991183.1 AlignFasta nevesk lThM.q - 400.0G >> 141.503G - 138.497G 0.645G 12.1d 14.8h 98.6% 20/mthread
14966194.92 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 91.596G - 91.596G 88.139G 3.8d 3.8d 99.6% 1
14969492.1 run_S5 szieba lThM.q - 1.0G << 139.303G - 139.303G 2.722G 43.5d 1.3d 65.9% 50/mthread
14969631.1 raxml-$TASK_ID gallego-narb lThM.q - 500.0G >> 3.151G - 3.133G 3.117G 19.1d 23.1h 99.2% 20/mthread
14966193.83 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 82.247G - 82.247G 79.087G 3.8d 3.8d 99.4% 1
14966190.55 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 61.426G - 61.426G 59.400G 3.8d 3.8d 99.5% 1
14969494.1 run_S5 szieba lThM.q - 1.0G << 139.286G - 139.286G 2.722G 44.9d 1.3d 68.7% 50/mthread
14970176.1 raxml-$TASK_ID gallego-narb lThM.q - 500.0G >> 1.858G - 1.852G 1.831G 18.5d 22.3h 99.3% 20/mthread
14969489.1 run_S5 szieba lThM.q - 1.0G << 141.635G - 141.635G 2.762G 51.5d 1.3d 77.5% 50/mthread
14966188.2 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 123.335G - 123.335G 118.407G 3.8d 3.8d 99.5% 1
14966192.73 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 47.226G - 47.226G 45.733G 3.8d 3.8d 99.7% 1
14966189.35 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 64.948G - 64.948G 62.072G 3.8d 3.8d 99.7% 1
|
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, 10-Jul-2026 10:21:11 EDT
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|