High-Memory Queues

Details on Jobs that Produced a Warning

As of Fri Mar 29 07:07:06 EDT 2024
   jobID.tID  jobName         user           queue  - mem_res  max(vmem) -   vmem     avgmem   cpu    age    eff. nslots
------------------------------------------------------------------------------------------------------------------------
24646007.1    Nat_6_3_getorga brandaor       mThM.q -  96.0G >>  31.404G -  24.955G  14.245G  21.2h  21.4h  12.4%     8/mthread
24646011.1    Nat_7_2_getorga brandaor       mThM.q -  96.0G >>  32.168G -  24.536G  13.580G  21.3h  21.4h  12.4%     8/mthread
24642157.1    Hym70p_sym      zhangy         mThM.q - 320.0G >>   4.778G -   4.449G   4.426G  52.2d   6.8d  48.0%    16/mthread
24643519.1    genetrees       zhangy         mThM.q - 480.0G >>  27.411G -  27.411G  21.460G  83.5d   3.5d  99.9%    24/mthread
24646009.1    Nat_6_5_getorga brandaor       mThM.q -  96.0G >>  40.987G -  25.888G  13.826G  21.3h  21.4h  12.5%     8/mthread
24642688.1    symGB237t_60ppS sossajef       lThM.q - 150.0G >>  31.596G -  31.533G  30.430G  81.5d   4.4d  93.3%    20/mthread
24646058.1    bcftools1.job   parkerld       lThM.q - 250.0G >>   0.623G -   0.576G   0.326G  20.0h  16.6h 120.4%     1
24642689.1    GB237t_60pSWSCE sossajef       lThM.q - 150.0G >>  38.302G -  38.168G  36.296G  81.2d   4.4d  93.0%    20/mthread
24642228.3    ngsLD           boltonp        lThM.q -  96.0G >>  37.947G -  37.234G  37.121G  47.8d   6.7d  59.8%    12/mthread
22914883.1    ngsLD_prune_gra connellym      lThM.q - 400.0G >>   4.196G -   4.163G   4.044G  34.0d  29.9d  56.9%     2/mthread
24642793.1    earl_grey_2     myerse         lThM.q - 600.0G >>  30.728G -  10.403G   0.331G  29.6d   3.7d  39.8%    20/mthread
22900132.1    BeastRep5       kressleinr     uThM.q -  64.0G >>  18.630G -  18.630G  18.409G 340.5d  41.8d  81.4%    10/mthread
22928731.1    masurca_2024.sh chaks        uTxlM.rq - 1.914T >> 669.945G - 441.256G 402.698G  56.0d  27.7d   5.0%    40/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 Friday, 29-Mar-2024 07:11:22 EDT with mk-web-page.pl ver. 6.3/1 (Dec 2023/SGK)