High-Memory Queues
Details on Jobs that Produced a Warning
As of Thu Jul 9 20:37:19 EDT 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
14991008.1 steve_22030FL_1 horowitzj mThM.q - 192.0G >> 28.134G - 11.409G 16.952G 16.9h 1.5h 69.6% 16/mthread
14987654.1 mf_test wirshingh mThM.q - 72.0G >> 9.338G - 1.383G 3.595G 9.3h 2.6h 40.3% 9/mthread
14991011.1 steve_22030FL_1 horowitzj mThM.q - 192.0G >> 30.135G - 0.664G 22.191G 15.7h 1.5h 64.6% 16/mthread
14991009.1 steve_22030FL_1 horowitzj mThM.q - 192.0G >> 31.377G - 31.377G 15.788G 17.8h 1.5h 73.5% 16/mthread
14966566.1 clNo_1000 peresph mThM.q - 20.0G >> 9.255G - 8.653G 8.573G 29.5d 3.0d 99.4% 10/mthread
14969201.1 mf_trimmedreads wirshingh mThM.q - 72.0G >> 34.366G - 0.963G 2.621G 4.1d 1.1d 40.3% 9/mthread
14991007.1 steve_22030FL_1 horowitzj mThM.q - 192.0G >> 26.484G - 21.776G 13.906G 17.5h 1.5h 72.2% 16/mthread
14966565.1 clcor1000 peresph mThM.q - 20.0G >> 7.636G - 7.390G 7.056G 29.6d 3.0d 99.5% 10/mthread
14969493.1 run_S5 szieba lThM.q - 1.0G << 139.458G - 139.458G 2.723G 27.4d 17.8h 74.2% 50/mthread
14991183.1 AlignFasta nevesk lThM.q - 400.0G >> 129.929G - 128.513G 0.639G 21.5h 1.1h 96.4% 20/mthread
14966194.92 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 91.596G - 91.596G 87.625G 3.2d 3.2d 99.6% 1
14969492.1 run_S5 szieba lThM.q - 1.0G << 139.221G - 139.221G 2.722G 23.0d 18.1h 61.0% 50/mthread
14969631.1 raxml-$TASK_ID gallego-narb lThM.q - 500.0G >> 3.151G - 3.138G 3.118G 7.8d 9.4h 99.0% 20/mthread
14966193.83 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 82.247G - 82.247G 78.614G 3.2d 3.2d 99.4% 1
14966190.55 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 61.426G - 61.426G 59.115G 3.2d 3.2d 99.5% 1
14969494.1 run_S5 szieba lThM.q - 1.0G << 139.260G - 139.260G 2.722G 24.7d 17.7h 66.9% 50/mthread
14970176.1 raxml-$TASK_ID gallego-narb lThM.q - 500.0G >> 1.858G - 1.847G 1.829G 7.1d 8.6h 99.3% 20/mthread
14969489.1 run_S5 szieba lThM.q - 1.0G << 141.395G - 141.395G 2.762G 27.4d 18.2h 72.0% 50/mthread
14966188.2 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 123.335G - 123.335G 117.623G 3.2d 3.2d 99.5% 1
14966192.73 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 47.226G - 47.226G 45.553G 3.2d 3.2d 99.7% 1
14966189.35 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 64.948G - 64.948G 61.649G 3.2d 3.2d 99.6% 1
14969503.14 imaging_array jmichail uThM.q - 70.0G > 60.498G - 54.722G 43.984G 9.1h 1.4h 665.0% 1
14966621.1 allee_cons_YGG0 graujh uTxlM.rq - 1.465T >> 48.356G - 27.781G 22.147G 2.6d 2.6d 1.6% 64/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, 09-Jul-2026 20:41:13 EDT
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|