The University of Arizona
    For questions, please open a UAService ticket and assign to the Tools Team.
Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

 

 

Disk Storage

 

When you obtain a new HPC account, you will be provided with the following storage:

  • /home/netid - 15GB    (backed up nightly)  
  • /extra/netid  -   200GB (no backups) *** Ocelote only *** 
  • /scratch/netid -  temp space, data removed nightly (no backups) ***Not available for Ocelote due to the new /extra***

Additional storage:

  • /xdisk/netid  -  200GB to 1TB available on request. The time limit is 45 days with one extension. This allocation is deleted after 45 days if no extension is requested. There are directory level quotas so any files in this directory count against this quota not matter who created it.  The data is not backed up.
  • /rsgrps/netid -  rented/purchased space  (no backups)

 

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.

xdisk

Use this link for details on xdisk usage

extra

/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.


Job Limits

Job Time Limits

 Each group is allocated a base of 24,000 hours of compute time, this allocation is refreshed monthly.  The allocation can be used on either the htc/cluster/smp clusters or on the new cluster, Ocelote., or a combination.

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. Reference the www.elgato.arizona.edu web site.

 

 

 

 

 

 

 

 

 PBS Batch Queue Limits

The batch queues on the different systems have the following memory, time and core limits.

 

 System 

 Queue Name

 # of Compute Nodes

Max CPU Hrs / Job

 Max Wallclock Hrs / Job

 Largest job

Total cores in use / group

 Largest job / memory

 Max # of Running Jobs

Max Queued Jobs

 Cluster (8400)

 standard

 124

 12,000

 240

 256 cores

512***

 512 GB

 512

500

 

 windfall

 229 (all)

12,000

 240

 256 cores

 

 512 GB

 512

 

 

 cluster_high

 105 (buy-in)

32,000

 720

 512 cores

 

 1024 GB

 1148

 

 

 

 

 

 

 

 

 

 

 

 SMP (UV1000)

 standard

 

 3,200

 240

 256 cores

512***

 512 GB

 512

500

 

 windfall

 

 3,200

 240

 256 cores

 

 512 GB

 256

 

 

 smp_high

 

 115,200

 720

 512 cores

 

 1280 GB

240

 

 

 

 

 

 

 

 

 

 

 

HTC 

 standard

 104

 12,000

 720

 256 cores

512***

 512 GB

 512

500

 

 windfall

 104

 12,000

 720

 256 cores

 

 512 GB

 512

 

 

 htc_high

 10

 12,000

 720

 512 cores

 

 512 GB

 240

 

 

 

 

 

 

 

 

 

 

 

 Ocelote

 standard

 331

 24,000

 240

 672** cores

1344***

 4032 GB

 500

2000

 

 windfall

 331

 24,000

 240

 672** cores

 

 4032 GB

 500

 

 

 high_pri

 36

 32,000

 720

 672** cores

 

 4032 GB

 500

 

 

**  This represents 24 physical nodes, and 4.6TB of memory
***  This limit is shared by all members of a group across all queues 

  • No labels