High-Memory Queues

Details on Jobs that Produced a Warning

As of Tue Feb 17 15:23:49 EST 2026
   jobID.tID  jobName         user           queue  - mem_res  max(vmem) -   vmem     avgmem   cpu    age    eff. nslots
------------------------------------------------------------------------------------------------------------------------
12198995.1    euk-SNP_array   johnsonsj      mThM.q -  40.0G >>  23.716G -  23.716G  23.638G   6.7h   2.2h 156.6%     2/mthread
12198995.2    euk-SNP_array   johnsonsj      mThM.q -  40.0G >>  23.609G -  23.525G  23.445G   6.6h   2.2h 152.9%     2/mthread
12198995.3    euk-SNP_array   johnsonsj      mThM.q -  40.0G >>  23.588G -  23.525G  23.450G   6.8h   2.2h 158.5%     2/mthread
12198995.4    euk-SNP_array   johnsonsj      mThM.q -  40.0G >>  23.656G -  23.652G  23.578G   7.2h   2.2h 167.2%     2/mthread
12198995.5    euk-SNP_array   johnsonsj      mThM.q -  40.0G >>  23.568G -  23.552G  23.458G   6.2h   2.2h 145.3%     2/mthread
12198798.1    Antho_199_spade granquistm     mThM.q - 160.0G >> 125.921G - 117.800G  50.012G   1.5d   4.5h  82.5%    10/mthread
12198817.1    Antho_218_spade granquistm     mThM.q - 160.0G >>  76.764G -  73.014G  28.604G  32.2h   3.9h  81.6%    10/mthread
12199002.1    angsd_make_saf_ beckerm        mThM.q -  80.0G >>   1.338G -   1.248G   1.110G   8.4h   2.0h  52.3%     8/mthread
12198818.1    Antho_219_spade granquistm     mThM.q - 160.0G >> 105.826G - 101.823G  31.255G  32.2h   3.9h  81.9%    10/mthread
12198795.1    Antho_196_spade granquistm     mThM.q - 160.0G >> 119.956G - 106.835G  50.877G   1.6d   4.5h  83.9%    10/mthread
12199000.1    align_bwa_grsp  friedmans2     mThM.q -  40.0G >>   5.730G -   4.133G   2.162G   6.9h   2.1h  81.5%     4/mthread
12199000.2    align_bwa_grsp  friedmans2     mThM.q -  40.0G >>   5.731G -   5.729G   2.080G   6.9h   2.1h  81.7%     4/mthread
12199000.3    align_bwa_grsp  friedmans2     mThM.q -  40.0G >>   5.820G -   5.728G   2.096G   7.0h   2.1h  82.3%     4/mthread
12198819.1    Antho_220_spade granquistm     mThM.q - 160.0G >>  73.295G -  73.295G  21.925G  32.1h   3.9h  81.9%    10/mthread
12190422.1    stairwayAZ.job  byerlyp        lThM.q -  20.0G >>   3.345G -   3.345G   3.308G  29.7h   1.2d  20.0%     5/mthread
12195552.1    stairwayNE.job  byerlyp        lThM.q -  20.0G >>   3.345G -   3.345G   3.307G  26.1h   1.1d  20.0%     5/mthread
12198654.1    xangsd_strict   uribeje        uThM.q - 200.0G >>  13.180G -  13.148G   9.378G   4.8d  22.4h  64.3%     8/mthread
11801118.1    angsd_strict    uribeje        uThM.q - 200.0G >> 157.164G - 156.186G 110.121G  30.7d  28.9d  13.3%     8/mthread
12198689.1    xPSMC1          uribeje        uThM.q - 400.0G >>  29.477G -  29.405G   9.854G  19.0h  10.0h  23.8%     8/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, 17-Feb-2026 15:31:11 EST with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)