High-Memory Queues

Details on Jobs that Produced a Warning

As of Wed Jul 8 03:37:06 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 -   8.422G   8.524G  12.5d   1.3d  99.3%    10/mthread
14966565.1    clcor1000       peresph        mThM.q -  20.0G >>   7.448G -   6.948G   6.999G  12.6d   1.3d  99.5%    10/mthread
14966194.92   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  91.596G -  91.596G  83.795G   1.5d   1.5d  99.6%     1
14966193.83   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  82.247G -  82.247G  75.083G   1.5d   1.5d  99.2%     1
14966190.55   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  61.426G -  61.426G  56.996G   1.5d   1.5d  99.5%     1
14968183.1    cerrado_RAxML_a nevesk         lThM.q - 300.0G >>  33.003G -  32.870G  32.377G  16.3d   6.2h  97.5%    64/mthread
14966224.1    run_opt_nrs1_ju szieba         lThM.q -   1.0G <<   1.074T -  22.413G   4.246G  14.6d   1.5d  16.3%    60/mthread
14514974.1    masurca_YGG054_ graujh         lThM.q - 448.0G >> 170.916G -   0.660G  20.271G 164.4d   7.4d  34.7%    64/mthread
14966225.1    run_opt_nrs2_ju szieba         lThM.q -   1.0G <<   1.134T -  27.537G   4.173G  12.9d   1.5d  14.5%    60/mthread
14966188.2    CJS_nbraw_nc    suttonm        lThM.q - 256.0G >> 123.335G - 123.335G 111.778G   1.5d   1.5d  99.3%     1
14966192.73   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  47.226G -  47.226G  44.210G   1.5d   1.5d  99.7%     1
14966189.35   CJS_nbraw_nc    suttonm        lThM.q - 256.0G >>  64.948G -  64.948G  58.499G   1.5d   1.5d  99.7%     1
14966621.1    allee_cons_YGG0 graujh       uTxlM.rq - 1.465T >>  48.340G -  47.754G  19.399G  20.9h  20.4h   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 Wednesday, 08-Jul-2026 03:41:09 EDT with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)