Service Unit (SU) Accounting

The Supercomputing Institute keeps track of machine usage using Service Units (SUs). Service Units awarded to a group can be used on any high performance system. If you have questions about accounting and monitoring usage, send an email to MSI support.

You can monitor your usage by using the command acctinfo. This command provides a summary of SU usage for the user executing it.

More information is provided below.

More about acctinfo

Users and Principal Investigators can see their combined usage for the current allocation period with the command  acctinfo.
Usage for previous allocation periods can be checked by specifying the year, e.g. to check 2014-2015:  acctinfo -y 2014

Along with SU usage acctinfo will report the percentage of usage remaining, days remaining in the allocation period and the percentage of days remaining in the allocation period.

Your group's fairshare targets and fairshare usage are also reported. For more information see: Fairshare Scheduling.

Example acctinfo Output

Below is an example acctinfo output for a Group Allocated non-PI user.

Accounting summary for the current period
Info for user testuser:
Data reflects jobs ending before Mon Dec  5 11:30:50 2011
All units are in SUs
   Group |  SU Type | Allocation |  Remaining | Accounting Type 
 testgroup | Standard |  270000.00 | 139943.59 ( 52% ) |   group ceiling 
                |  Koronis  |       0.00      | 0.00 (  0% ) |                 
The time remaining in this period is 27 days, or 7% of the period.
Standard SUs by user:
    User |       Used |       Used |     Used 
             |      Calho |      Casca |    Itasc 
 testuser |               |                 |    6254.06 
Your group's fairshare target is 0.04%.
Your group's usage on this particular system is 0.01%.
Fairshare is one of the many factors used in the calculation of job priority.  
If you have exceeded your fairshare target, your jobs will have a lower priority


Determining/ Calculating SU charges

Service Units (SUs) are charged for computer time on HPC resources.

One SU will provide a fixed number of hours of CPU time as follows and for detailed hardware specifications, click on the system name in the following table:

CPU Hours per SU for MSI HPC Resources
HPC Resource CPU hours/SU
Itasca 1.5
Mesabi 1.5

To determine the number of SUs you require you will need to know:
      a. how many processors (cores) your program runs on, 
      b.  how long each run takes (in hours), and
      c. how many runs you plan to do. 
The product of these three numbers determines how many CPU hours you will need. Dividing the required CPU hours by the appropriate CPU-to-SU conversion factor found above will determine the number of SUs needed on the chosen machine. 
The table below provides a few examples for the Itasca systems:

Example SU Calculations
Application Information CPU Hour Calculation Itasca SUs
a single-core application that takes 5.5 hours per run; 190 runs will be needed 1 core x 5.5 hours x 190 runs = 1,045 CPU-HRs Not Allowed
a 128-core application that takes 19 hours per run; 500 runs will be needed 128 cores x 19 hours x 500 runs = 1,216,000 CPU-HRs 1,216,000 CPU-HRs / 1.5 CPU-HRs per SU = 810,667 SUs
a 2,048-core application that takes 24 hours per run; 75 runs will be needed 2,048 cores x 24 hours x 75 runs = 3,686,400 CPU-HRs 3,686,400 CPU-HRs / 1.5 CPU-HRs per SU = 2,457,600 SUs

Please see the Allocations page for details on Service Unit allocation eligibility, renewal, and the peer review allocation process.