High-Memory Queues

Details on Jobs that Produced a Warning

As of Thu Jul 30 13:27:08 EDT 2026 
   jobID.tID  jobName         user           queue  - mem_res  max(vmem) -   vmem     avgmem   cpu    age    eff. nslots
------------------------------------------------------------------------------------------------------------------------
15302149.1    assemble-spades lealc          mThM.q - 200.0G >> 127.866G -   0.702G  13.910G  12.1d  22.0h  82.5%    16/mthread
15298719.1    mf_trm2         wirshingh      mThM.q -  72.0G >   68.102G -   2.942G   2.901G  10.9d   3.1d  39.3%     9/mthread
15301656.2    earlgrey        zhangy         lThM.q - 192.0G >>   7.794G -   1.870G   1.545G   9.2d   1.2d  61.8%    12/mthread
15301656.3    earlgrey        zhangy         lThM.q - 192.0G >>  43.915G -   2.548G   1.155G  12.6d   1.2d  84.9%    12/mthread
15301656.5    earlgrey        zhangy         lThM.q - 192.0G >>  25.578G -   0.728G   1.643G   9.8d   1.2d  65.9%    12/mthread
15301656.6    earlgrey        zhangy         lThM.q - 192.0G >>   9.698G -   4.013G   1.577G  10.3d   1.2d  69.5%    12/mthread
15293594.1    raxml_hmem      athalappila    lThM.q - 120.0G >>  71.743G -  71.276G  70.797G 274.0d   7.0d  98.6%    40/mthread
15300160.9    imaging_array   jmichail       uThM.q -  70.0G >>  53.319G -  49.508G  47.055G  26.0h  21.3h 122.3%     1
15300160.12   imaging_array   jmichail       uThM.q -  70.0G >   65.919G -  62.304G  53.581G  26.6h   8.9h 299.7%     1
15300160.13   imaging_array   jmichail       uThM.q -  70.0G >   59.855G -  53.032G  46.388G  18.8h   5.2h 359.4%     1
15300040.1    Hifi_P2_HICdata gonzalezv    uTxlM.rq - 1.758T >>  31.174G -  10.713G  11.009G  21.2d   1.8d  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 13:31:09 EDT with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)