HPC3 - Reference Guide

1. Acceptable Use Policy

HPC3 is a shared facility. Please be aware that there may be 100+ active users logged in at any particular time. What you do can have dramatic effects on others. Please read and abide by the Acceptable Use Policy for resources managed by the Research Cyberinfrastructure Center at UCI. Violations of this policy or any other applicable University policies may result in the temporary or permanent removal of accounts associated with research computing.

2. Quick Start

Please see Step by Step Howto for information on how to get account and login.

3. Storage

The storage is generally in 3 areas. Please see HOME, DFS, and CRSP filesystems

4. Free and Accounted Jobs

There is no cost for a user to obtain an account on HPC3, we delete inactive accounts after 1 year of no activity. HPC3 dispenses with the idea of "owner" queues. Instead, jobs are classified into two types:

Accounted

The core-hours = #cores X wall-time used by your job is charged to an account. Any job running this way cannot be killed or pre-empted by another job. When the job completes, the core hours (or GPU hours) are debited from an account.

Free

Jobs can run without charging an account in the free partition. Free jobs can get killed by another accounted job (without warning). Maximum run times are more limited for free jobs.

There is no checkpointing facility.
  1. Every user on HPC3 is given a one-time allotment of 1000 core hours

    • This is the account balance for personal use

    • This number is NOT re-filled.

    • If you have no other account to charge, you can use this account or the free queues.

  2. Any UCI faculty who request an account will be granted 200,0001 no-cost CPU hours

    • These are hours per fiscal year, allocated in increments every 6 months2

    • Unused hours can not be replenished later.

    • Any UCI Professor can request an HPC3 lab account on behalf of their research group and add any number of researchers/students to this account. They have complete control over who can charge to their account and can put spending limits on any person.

1Based upon the number of requests and the number of nodes purchased by RCIC, this number will vary.

2Based on the unused hours the increment amount will vary

Condo owners have their systems converted into core hours. For example, a 40-core system can deliver (with no downtime) a maximum of 350K core hours every year. Each year that a physical condo node is in the cluster, 95% percent of the condo nodes' theoretical maximum is deposited into the owner’s account.

5. Hardware specs and purchasing