Low CPU percent indicates that the amount of work being done on a node is much less than what is possible. In the example below, the average load per node is 0.01 (line 4) when it should be closer to 20 (line 3). Memory utilization in this case is also very small (line 13). User account information is summarized in lines 31 - 40.

 1)  E135 - Low CPU percent
 2)  The average CPU percent per node is low: 0%
 3)  The average CPU percent should be: 2000%
 4)  Average load per node: 0.01
 5)  The average memory usage per node: 1381mb, 2%
 6)  Try to use CPU and memory resources wisely.
 7)
 8)  Node statistics::
 9)  Number of nodes: 64
10)  Number of cores: 1280
11)  Total physical memory per node: 64364mb
12)  Average memory usage per node: 1381mb, 2%
13)  Average memory usage per core: 69mb
14)  Average virtual memory usage per node: 2561mb
15)  Average virtual memory usage per core: 128mb
16)  Average CPU percent per node: 0%
17)  Average CPU percent per core: 0%
18)  Average load per node: 0.01
19)  Reverified average load per node: 12.19
20)  Effective maximum load on a node: 17.74
21)
22)  PBS_job=78212.smic3 user=flast allocation=hpc_alloc03
23)  queue=workq total_load=0.72 cpu_hours=0.00 wall_hours=1.05
24)  unused_nodes=0 total_nodes=64 ppn=20 avg_load=0.01 avg_cpu=0%
25)  avg_mem=1381mb avg_vmem=2561mb
26)  top_proc=flast:ddt-debugger:smic256:221M:7M:0.0hr:2%
27)  toppm=flast:gdb:smic035:1456M:1339M node_processes=8
28)  avg_avail_mem=60882mb min_avail_mem=56724mb
29)  reverified_avg_load=12.19
30)
31)  Name:  First Last
32)  Mail:  flast@somewhere.lsu.edu
33)  Affil: First Last
34)  Category:
35)  Name:  First Last
36)  Mail:  flast@somewhere.lsu.edu
37)  Affil: First Last
38)  Category: validation:current:03/14/2011
39)  Allocations:
40)  hpc_alloc03,flast,12813004.16,default