All University of Arizona Principal Investigators (PIs; aka Faculty) that register for access to the UA High Performance Computing (HPC) receive allocation on the HPC machines. Currently all PIs receive:
When you obtain a new HPC account, you will be provided with the following storage:
File count limit:
We strongly recommend that you do some regular housekeeping of your allocated space. Millions of files are hard to keep organized and even more difficult to migrate. Archiving or using a tool like tar will help keep our disk arrays efficient and potentially free up more space for you to use.
Use this link for details on xdisk usage
/extra is something new with Ocelote. When you log in to Ocelote for the first time, an allocation of 200GB will be created for you. It takes an hour or two to show up, and then it is permanent. Remember that it is not backed up like /home. The number of files within the 200GB is limited to 120,000.
uquota is the command to display how much space you have used / remaining
Job Time Limits
Each group is allocated a base of 36,000 hours of compute time. This allocation is refreshed monthly. This allocation can be subdivided by the PI using the portal at https://portal.hpc.arizona.edu/portal/
The command va will display your remaining time
You can use this time on either the standard nodes which do not require special attributes in the scheduler script, or on the GPU nodes which do require special attributes. The queues are setup so that jobs that do not request GPU's will not run there.
ElGato has a different allocation method of time as it is funded through an NSF MRI grant with usage time provided for campus researchers outside of the grant recipients.
PBS Batch Queue Limits
The batch queues on the different systems have the following memory, time and core limits.
|debug||Used as a high priority to test code or jobs.|
|standard||Used to consume the monthly allocation of hours provided to each group|
|windfall||Used when standard is depleted but subject to preemption|
|high_priority||Used by 'buy-in' users for purchased nodes|
# of Compute Nodes
Max Wallclock Hrs / Job
|Total cores in use / group|
Largest job / memory
Max # of Running Jobs
|Max Queued Jobs|
*** This limit is shared by all members of a group across all queues. So you can use the system 2016 core limit by one user on the standard queue or share it across multiple users or queues.