This command shows various accounting and resource usage statistics for the system. Historical statistics cover the timeframe from the most recent execution of the resetstats command.
Access
By default, this command can be run by any Moab level 1, 2, or 3 Administrator.
Parameters
Flag
Description
-a [<ACCOUNTID>]
display account statistics
-c [<CLASSID>]
display class statistics
-f
display full matrix statistics (see showstats -f for full details)
display summary information. NOTE: only valid with the '-n' flag
-t
display statistical information from the specified timeframe:
-T
display fairshare tree statistics
-u [<USERID>]
display user statistics
-v
display verbose information
Example 1
This example shows a statistical listing of all active accounts. The top
line (Account Statistics Initialized...) of the output indicates the beginning
of the timeframe covered by the displayed statistics.
The statistical output is divided into two categories, Running and Completed.
Running statistics include information about jobs that are currently running.
Completed statistics are compiled using historical information from both
running and completed jobs.
The fields are as follows:
Account
Account Number.
Jobs
Number of running jobs.
Procs
Number of processors allocated to running jobs.
ProcHours
Number of proc-hours required to complete running jobs.
Jobs*
Number of jobs completed.
%
Percentage of total jobs that were completed by account.
PHReq*
Total proc-hours requested by completed jobs.
%
Percentage of total proc-hours requested by completed jobs that were
requested by account.
PHDed
Total proc-hours dedicated to active and completed jobs. The proc-hours
dedicated to a job are calculated by multiplying the number of allocated
procs by the length of time the procs were allocated, regardless of the
job's CPU usage.
%
Percentage of total proc-hours dedicated that were dedicated by account.
FSTgt
Fairshare target. An account's fairshare target is specified in the
fs.cfg
file. This value should be compared to the account's node-hour dedicated
percentage to determine if the target is being met.
AvgXF*
Average expansion factor for jobs completed. A job's XFactor (expansion
factor) is calculated by the following formula: (QueuedTime + RunTime)
/ WallClockLimit.
MaxXF*
Highest expansion factor received by jobs completed.
AvgQH*
Average queue time (in hours) of jobs.
Effic
Average job efficiency. Job efficiency is calculated by dividing the
actual node-hours of CPU time used by the job by the node-hours allocated
to the job.
WCAcc*
Average wall clock accuracy for jobs completed. Wall clock accuracy
is calculated by dividing a job's actual run time by its specified wall
clock limit. NOTE: A job's wallclock accuracy is capped at 100% so even if a job exceeds its requested walltime it will report an accuracy of 100%
* These fields are empty until an account has completed
at least one job.
Example 2
This example shows a statistical listing of all active groups. The top
line (Group Statistics Initialized...) of the output indicates the beginning
of the timeframe covered by the displayed statistics.
The statistical output is divided into two categories, Running and Completed.
Running statistics include information about jobs that are currently running.
Completed statistics are compiled using historical information from both
running and completed jobs.
The fields are as follows:
GroupName
Name of group.
GID
Group ID of group.
Jobs
Number of running jobs.
Procs
Number of procs allocated to running jobs.
ProcHours
Number of proc-hours required to complete running jobs.
Jobs*
Number of jobs completed.
%
Percentage of total jobs that were completed by group.
PHReq*
Total proc-hours requested by completed jobs.
%
Percentage of total proc-hours requested by completed jobs that were
requested by group.
PHDed
Total proc-hours dedicated to active and completed jobs. The proc-hours
dedicated to a job are calculated by multiplying the number of allocated
procs by the length of time the procs were allocated, regardless of the
job's CPU usage.
%
Percentage of total proc-hours dedicated that were dedicated by group.
FSTgt
Fairshare target. A group's fairshare target is specified in the fs.cfg
file. This value should be compared to the group's node-hour dedicated
percentage to determine if the target is being met.
AvgXF*
Average expansion factor for jobs completed. A job's XFactor (expansion
factor) is calculated by the following formula: (QueuedTime + RunTime)
/ WallClockLimit.
MaxXF*
Highest expansion factor received by jobs completed.
AvgQH*
Average queue time (in hours) of jobs.
Effic
Average job efficiency. Job efficiency is calculated by dividing the
actual node-hours of CPU time used by the job by the node-hours allocated
to the job.
WCAcc*
Average wall clock accuracy for jobs completed. Wall clock accuracy
is calculated by dividing a job's actual run time by its specified wall
clock limit.NOTE: A job's wallclock accuracy is capped at 100% so even if a job exceeds its requested walltime it will report an accuracy of 100%
* These fields are empty until a group has completed at
least one job.
Example 3
Example 4
This example shows a concise summary of the system scheduling state.
Note that
showstats and showstats -s are equivalent.
The first line of output indicates the number of scheduling iterations
performed by the current scheduling process, followed by the time the scheduler
started. The second line indicates the amount of time the Moab Scheduler
has been scheduling in HH:MM:SS notation followed by the statistics initialization
time.
The fields are as follows:
Active Jobs
Number of jobs currently active (Running or Starting).
Eligible Jobs
Number of jobs in the system queue (jobs that are considered when scheduling).
Idle Jobs
Number of jobs both in and out of the system queue that are in the
LoadLeveler Idle state.
Completed Jobs
Number of jobs completed since statistics were initialized.
Successful Jobs
Jobs that completed successfully without abnormal termination.
XFactor
Average expansion factor of all completed jobs.
Max XFactor
Maximum expansion factor of completed jobs.
Max Bypass
Maximum bypass of completed jobs.
Available ProcHours
Total proc-hours available to the scheduler.
Dedicated ProcHours
Total proc-hours made available to jobs.
Effic
Scheduling efficiency (DedicatedProcHours / Available ProcHours).
Min Efficiency
Minimum scheduling efficiency obtained since scheduler was started.
Iteration
Iteration on which the minimum scheduling efficiency occurred.
Available Procs
Number of procs currently available.
Busy Procs
Number of procs currently busy.
Effic
Current system efficiency (BusyProcs/AvailableProcs).
WallClock Accuracy
Average wall clock accuracy of completed jobs (job-weighted average).
Job Efficiency
Average job efficiency (UtilizedTime / DedicatedTime).
Est Backlog
Estimated backlog of queued work in hours.
Avg Backlog
Average backlog of queued work in hours.
Example 5
This example shows a statistical listing of all active users. The top line
(User Statistics Initialized...) of the output indicates the timeframe
covered by the displayed statistics.
The statistical output is divided into two statistics categories, Running
and Completed. Running statistics include information about jobs that are
currently running. Completed statistics are compiled using historical information
from both running and completed jobs.
The fields are as follows:
UserName
Name of user.
UID
User ID of user.
Jobs
Number of running jobs.
Procs
Number of procs allocated to running jobs.
ProcHours
Number of proc-hours required to complete running jobs.
Jobs*
Number of jobs completed.
%
Percentage of total jobs that were completed by user.
PHReq*
Total proc-hours requested by completed jobs.
%
Percentage of total proc-hours requested by completed jobs that were
requested by user.
PHDed
Total proc-hours dedicated to active and completed jobs. The proc-hours
dedicated to a job are calculated by multiplying the number of allocated
procs by the length of time the procs were allocated, regardless of the
job's CPU usage.
%
Percentage of total prochours dedicated that were dedicated by user.
FSTgt
Fairshare target. A user's fairshare target is specified in the fs.cfg
file. This value should be compared to the user's node-hour dedicated percentage
to determine if the target is being met.
AvgXF*
Average expansion factor for jobs completed. A job's XFactor (expansion
factor) is calculated by the following formula: (QueuedTime + RunTime)
/ WallClockLimit.
MaxXF*
Highest expansion factor received by jobs completed.
AvgQH*
Average queue time (in hours) of jobs.
Effic
Average job efficiency. Job efficiency is calculated by dividing the
actual node-hours of CPU time used by the job by the node-hours allocated
to the job.
WCAcc*
Average wallclock accuracy for jobs completed. Wallclock accuracy is calculated by dividing a job's actual run time by its specified wallclock limit. NOTE: A job's wallclock accuracy is capped at 100% so even if a job exceeds its requested walltime it will report an accuracy of 100%
* These fields are empty until a user has completed at
least one job.