Page History
Contributed By
| Contributors |
|---|
Gadi is Australia’s most powerful supercomputer, a highly parallel cluster comprising more than 150,000 processor cores on ten different types of compute nodes. Gadi accommodates a wide range of tasks, from running climate models to genome sequencing, from designing molecules to astrophysical modelling. To start using Gadi, you should read this page which covers most of the basics you need to know before submitting your first job.
...
| Resource Name | Owner | Accessible from | Size Limit | Allocation Valid Until | Resource Specific Comments | |
|---|---|---|---|---|---|---|
| Compute Hours | project | n.a. | amount set by scheme manager | end of quarter | ||
| storage | $HOME | user | PBS jobs / login nodes | 10 GiB with no possible extension | user account deactivation |
|
/scratch/$PROJECT | project | PBS jobs† / login nodes | 72 GiB by default, more on jobs' demand | project retirement/job demand changes |
| |
/g/data/$PROJECT | project | PBS jobs† / login nodes | amount set by scheme manager | project retirement |
| |
| mdss | project | PBS copyq jobs† / login nodes | amount set by scheme manager | project retirement tape-based archival data sto |
| |
| $PBS_JOBFS | user | PBS jobs * | disk space available on the job's hosting node(s) | job termination |
| |
| software applications | NCI | PBS jobs / login nodes | n.a. | n.a. |
| |
| license | software group owner | PBS jobs / login nodes | available seats on the licensing server | license expiry date |
| |
...
This shows the total, used, reserved, and available compute grant of the project in the current billing period at the time of the query. SU is short for Service Unit, the unit that measures Gadi compute hours. Jobs run on the Gadi normal queue are charged 2 SUs to run for an hour on a single core with a memory allocation of up to 4 GiB. Jobs on Gadi are charged for the proportion of a node’s total memory that is used: see more examples of job cost here. In addition, different Gadi queues have different charge rates: see the breakdown of charge rates here.
The Grant amount listed is always equal to the sum of Used, Reserved and Avail. Every time a project has a job submitted, its potential cost, calculated according to the requested walltime, is reserved from the total Grant and reduces the amount of Avail. The actual cost based on walltime usage is determined only after the job's completion. If it finishes within the requested walltime limit, the over-reserved allocation is returned to the Avail amount and the actual cost goes to Used amount. When the project has no jobs that are waiting to run or running, Reserved SU returns to zero.
...
The first column in the output shows the permissions set for the folder/file. For more information on unix file permissions, see this page.
To look up how much storage you have access to through which projects, run the command ‘lquota’ on the login node. It prints out the storage allocation info together with its live usage data. For example, the return message
...
Overview
Content Tools