High-Memory Queues

Details on Jobs that Produced a Warning

As of Tue Jul 7 20:27:07 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.249G -   9.231G   8.475G   9.6d  23.1h  99.3%    10/mthread
14967091.1    metaspades      breusingc      mThM.q -   0.0G << 206.081G - 141.026G  68.237G   3.7d   7.6h  73.6%    16/mthread
14966565.1    clcor1000       peresph        mThM.q -  20.0G >>   7.448G -   7.323G   6.997G   9.6d  23.1h  99.5%    10/mthread
14966194.92   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  91.596G -  91.596G  82.039G  29.6h   1.2d  99.6%     1
14966193.83   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  82.247G -  82.247G  73.466G  29.5h   1.2d  99.2%     1
14966190.55   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  61.426G -  61.426G  56.023G  29.6h   1.2d  99.5%     1
14966224.1    run_opt_nrs1_ju szieba         lThM.q -   1.0G << 976.761G - 211.045G   3.823G  12.8d   1.2d  17.9%    60/mthread
14514974.1    masurca_YGG054_ graujh         lThM.q - 448.0G >> 170.916G -  55.790G  20.792G 159.9d   7.1d  35.1%    64/mthread
14966225.1    run_opt_nrs2_ju szieba         lThM.q -   1.0G <<   1.124T -  12.541G   3.997G  10.6d   1.2d  14.9%    60/mthread
14966188.2    CJS_nbraw_nc    suttonm        lThM.q - 256.0G >> 123.335G - 123.335G 109.108G  29.5h   1.2d  99.4%     1
14966192.73   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  47.226G -  47.226G  43.595G  29.6h   1.2d  99.6%     1
14966189.35   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  64.948G -  64.948G  57.055G  29.6h   1.2d  99.6%     1
14966621.1    allee_cons_YGG0 graujh       uTxlM.rq - 1.465T >>  48.293G -  47.856G  26.867G  13.7h  13.2h   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 Tuesday, 07-Jul-2026 20:31:12 EDT with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)