Up since 11/8/17 02:45 pm


Up since 11/14/17 11:20 pm


Up since 10/17/17 05:40 pm


Up since 11/20/17 09:15 am


Up since 11/15/17 07:25 am


Up since 11/27/17 10:45 am
OLCF User Assistance Center

Can't find the information you need below? Need advice from a real person? We're here to help.

OLCF support consultants are available to respond to your emails and phone calls from 9:00 a.m. to 5:00 p.m. EST, Monday through Friday, exclusive of holidays. Emails received outside of regular support hours will be addressed the next business day.

Eos Job Resource Accounting

See this article in context within the following user guides: Eos
Charging Factor

To match the charge factor for Titan, the usage factor for Eos will be set at 30 times nodes requested. The actual number of cores per nodes is 16 without Intel Hyper Threading (default) or 32 with Intel Hyper Threading enabled (-j2 aprun option). If you use showq to check your job’s allocation, it will show the number of cores requested in multiples of 32 regardless of  the chosen Hyper Threading options or utilized number of cores. This is because the scheduler must be set to allocate the potential maximum number of cores per node to enable all the possible ways of utilizing the node. This does not effect the aprun options you have chosen and will not change the 30 times per node usage factor. 

Note: Whole nodes must be requested at the time of job submission regardless of actual CPU or GPU core utilization.
Viewing Allocation Utilization

Projects are allocated time on Eos in units of “Eos core-hours”. Other OLCF systems are allocated in units of “core-hours”. This page describes how such units are calculated, and how users can access more detailed information on their relevant allocations.

Eos Core-Hour Calculation

The Eos core-hour charge for each batch job will be calculated as follows:

Eos core-hours = nodes requested * 30 * ( batch job endtime - batch job starttime )

Where batch job starttime is the time the job moves into a running state, and batch job endtime is the time the job exits a running state.

A batch job’s usage is calculated solely on requested nodes and the batch job’s start and end time. The number of cores actually used within any particular node within the batch job is not used in the calculation. For example, if a job requests 64 nodes through the batch script, runs for an hour, uses only 2 CPU cores per node, the job will still be charged for 64 * 30 * 1 = 1,920 Eos core-hours.

Viewing Usage

Utilization is calculated daily using batch jobs which complete between 00:00 and 23:59 of the previous day. For example, if a job moves into a run state on Tuesday and completes Wednesday, the job’s utilization will be recorded Thursday. Only batch jobs which write an end record are used to calculate utilization. Batch jobs which do not write end records due to system failure or other reasons are not used when calculating utilization.

Each user may view usage for projects on which they are members from the command line tool showusage and the My OLCF site.

On the Command Line via showusage

The showusage utility can be used to view your usage from January 01 through midnight of the previous day. For example:

$ showusage
Usage on Eos:
                                  Project Totals          <userid>
 Project      Allocation        Usage    Remaining          Usage
 <YourProj>    2000000   |   123456.78   1876543.22  |     1560.80

The -h option will list more usage details.

On the Web via My OLCF

More detailed metrics may be found on each project’s usage section of the My OLCF site.

The following information is available for each project:

  • YTD usage by system, subproject, and project member
  • Monthly usage by system, subproject, and project member
  • YTD usage by job size groupings for each system, subproject, and project member
  • Weekly usage by job size groupings for each system, and subproject
  • Batch system priorities by project and subproject
  • Project members

The My OLCF site is provided to aid in the utilization and management of OLCF allocations. If you have any questions or have a request for additional data, please contact the OLCF User Assistance Center.