High-Memory Queues
Details on Jobs that Produced a Warning
As of Thu Jul 9 00:37:18 EDT 2026
jobID.tID jobName user queue - mem_res max(vmem) - vmem avgmem cpu age eff. nslots
------------------------------------------------------------------------------------------------------------------------
14969204.3 x_alignment willishr mThM.q - 40.0G >> 11.539G - 4.173G 2.536G 2.2d 6.8h 94.5% 8/mthread
14969204.5 x_alignment willishr mThM.q - 40.0G >> 10.384G - 0.693G 2.536G 2.3d 6.8h 100.8% 8/mthread
14969204.8 x_alignment willishr mThM.q - 40.0G >> 10.663G - 10.382G 2.374G 2.3d 6.8h 100.9% 8/mthread
14969204.9 x_alignment willishr mThM.q - 40.0G >> 12.058G - 11.904G 2.393G 2.3d 6.8h 101.0% 8/mthread
14969204.10 x_alignment willishr mThM.q - 40.0G >> 12.008G - 11.541G 2.041G 2.3d 6.8h 100.9% 8/mthread
14969204.13 x_alignment willishr mThM.q - 40.0G >> 10.762G - 4.110G 2.524G 2.0d 6.8h 88.5% 8/mthread
14969204.14 x_alignment willishr mThM.q - 40.0G >> 10.635G - 4.110G 2.486G 2.2d 6.8h 97.7% 8/mthread
14969204.16 x_alignment willishr mThM.q - 40.0G >> 10.384G - 3.983G 2.550G 2.2d 6.8h 95.9% 8/mthread
14969204.17 x_alignment willishr mThM.q - 40.0G >> 10.760G - 4.046G 2.578G 2.1d 6.8h 91.0% 8/mthread
14969204.6 x_alignment willishr mThM.q - 40.0G >> 12.058G - 11.966G 2.384G 2.3d 6.8h 101.0% 8/mthread
14969204.18 x_alignment willishr mThM.q - 40.0G >> 10.384G - 4.046G 2.585G 1.9d 6.8h 83.4% 8/mthread
14969204.19 x_alignment willishr mThM.q - 40.0G >> 10.568G - 4.046G 2.570G 2.0d 6.8h 86.0% 8/mthread
14969204.12 x_alignment willishr mThM.q - 40.0G >> 10.384G - 4.110G 2.394G 2.0d 6.8h 88.7% 8/mthread
14969204.21 x_alignment willishr mThM.q - 40.0G >> 12.058G - 11.961G 2.430G 2.3d 6.8h 100.3% 8/mthread
14969204.15 x_alignment willishr mThM.q - 40.0G >> 10.765G - 10.195G 2.324G 2.3d 6.8h 101.0% 8/mthread
14969204.22 x_alignment willishr mThM.q - 40.0G >> 12.090G - 4.046G 2.808G 2.1d 6.8h 92.6% 8/mthread
14969204.25 x_alignment willishr mThM.q - 40.0G >> 10.507G - 3.983G 2.539G 2.0d 6.8h 88.1% 8/mthread
14969204.7 x_alignment willishr mThM.q - 40.0G >> 12.058G - 11.603G 2.487G 2.3d 6.8h 100.1% 8/mthread
14966566.1 clNo_1000 peresph mThM.q - 20.0G >> 9.249G - 8.557G 8.541G 21.2d 2.1d 99.4% 10/mthread
14969201.1 mf_trimmedreads wirshingh mThM.q - 72.0G >> 34.306G - 3.395G 3.155G 24.8h 6.9h 39.9% 9/mthread
14969176.1 loco-pipe-N187- longk mThM.q - 320.0G >> 99.113G - 67.267G 1.761G 7.6d 7.5h 75.6% 32/mthread
14966565.1 clcor1000 peresph mThM.q - 20.0G >> 7.636G - 7.136G 7.019G 21.3d 2.1d 99.5% 10/mthread
14966194.92 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 91.596G - 91.596G 86.435G 2.4d 2.4d 99.6% 1
14966193.83 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 82.247G - 82.247G 77.517G 2.4d 2.4d 99.3% 1
14966190.55 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 61.426G - 61.426G 58.457G 2.4d 2.4d 99.5% 1
14969203.1 run_pacman_swee szieba lThM.q - 1.0G << 4.972G - 4.847G 4.141G 8.4h 6.8h 2.5% 50/mthread
14966188.2 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 123.335G - 123.335G 115.809G 2.4d 2.4d 99.5% 1
14966192.73 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 47.226G - 47.226G 45.135G 2.4d 2.4d 99.7% 1
14966189.35 CJS_nbraw_nc suttonm lThM.q - 256.0G >> 64.948G - 64.948G 60.670G 2.4d 2.4d 99.7% 1
14968702.10 imaging_array jmichail uThM.q - 70.0G >> 55.884G - 48.942G 43.893G 10.9h 1.9h 569.0% 1
14968702.11 imaging_array jmichail uThM.q - 70.0G >> 53.590G - 52.070G 43.717G 8.8h 1.0h 838.8% 1
14966621.1 allee_cons_YGG0 graujh uTxlM.rq - 1.465T >> 48.356G - 29.206G 18.989G 1.7d 1.7d 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
Thursday, 09-Jul-2026 00:41:14 EDT
with mk-web-page.pl ver. 7.3/1 (Oct 2025/SGK)
|