High-Memory Queues

Details on Jobs that Produced a Warning

As of Thu Jul 9 17:28:32 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.558G   8.569G  28.2d   2.8d  99.4%    10/mthread
14969201.1    mf_trimmedreads wirshingh      mThM.q -  72.0G >>  34.306G -   2.079G   2.624G   3.6d  23.8h  40.3%     9/mthread
14985137.1    nexflow_testmod ariasc         mThM.q - 750.0G >> 149.348G -  79.423G  23.014G   9.3h   0.4h  68.8%    30/mthread
14966565.1    clcor1000       peresph        mThM.q -  20.0G >>   7.636G -   7.136G   7.053G  28.3d   2.8d  99.5%    10/mthread
14969493.1    run_S5          szieba         lThM.q -   1.0G << 139.380G - 139.380G   2.723G  22.1d  14.6h  72.8%    50/mthread
14966194.92   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  91.596G -  91.596G  87.479G   3.1d   3.1d  99.6%     1
14969492.1    run_S5          szieba         lThM.q -   1.0G << 139.218G - 139.218G   2.722G  18.0d  14.9h  58.1%    50/mthread
14969631.1    raxml-$TASK_ID  gallego-narb   lThM.q - 500.0G >>   3.151G -   3.138G   3.117G   5.2d   6.3h  98.9%    20/mthread
14966193.83   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  82.247G -  82.247G  78.479G   3.1d   3.1d  99.4%     1
14966190.55   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  61.426G -  61.426G  59.035G   3.1d   3.1d  99.5%     1
14969494.1    run_S5          szieba         lThM.q -   1.0G << 139.191G - 139.191G   2.722G  19.9d  14.6h  65.6%    50/mthread
14969495.1    run_S5          szieba         lThM.q -   1.0G << 140.372G - 140.372G   2.744G  25.2d  14.5h  83.5%    50/mthread
14970176.1    raxml-$TASK_ID  gallego-narb   lThM.q - 500.0G >>   1.858G -   1.848G   1.829G   4.5d   5.5h  99.1%    20/mthread
14969489.1    run_S5          szieba         lThM.q -   1.0G << 141.378G - 141.378G   2.762G  22.3d  15.1h  71.1%    50/mthread
14966188.2    CJS_nbraw_nc    suttonm        lThM.q - 256.0G >> 123.335G - 123.335G 117.402G   3.1d   3.1d  99.5%     1
14966192.73   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  47.226G -  47.226G  45.502G   3.1d   3.1d  99.7%     1
14966189.35   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  64.948G -  64.948G  61.530G   3.1d   3.1d  99.7%     1
14969503.9    imaging_array   jmichail       uThM.q -  70.0G >   61.421G -  35.671G  49.283G  21.7h   3.6h 608.5%     1
14969503.11   imaging_array   jmichail       uThM.q -  70.0G >   61.823G -  54.613G  45.385G  10.1h   3.4h 294.1%     1
14966621.1    allee_cons_YGG0 graujh       uTxlM.rq - 1.465T >>  48.356G -  27.781G  21.849G   2.5d   2.4d   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 17:31:13 EDT with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)