Debug and Development Partitions
Excerpt | ||
---|---|---|
| ||
Partitions dedicated for debugging and code development are restricted for these two tasks and nothing else. Therefore, this kind of partitions should never be utilised for production runs (even if the execution time of these jobs is under the walltime limit of the debug/development partition). Debug and development partitions are easily identified with names like
These partitions must not be used for the following activities:
Note: This restriction applies regardless of the execution time of the jobs. For instance, jobs that involve testing for numerical stability, parameter optimization, or early-stage simulations should not be conducted on the Debug/Development partitions, even if the run times are under the partition's walltime limit. |
Current available debug and development partitions at Pawsey are:
Cluster | Name | N. Nodes | Cores per node | Available node-RAM for jobs | GPU chiplets per node | Types of jobs supported | Max Number of Nodes per Job | Max Wall time | Max Number of Concurrent Jobs per User | Max Number of Jobs Submitted per User |
---|---|---|---|---|---|---|---|---|---|---|
Setonix | debug | 8 | 2x 64 | 230 GB | n/a | Exclusive for development and debugging of CPU code and workflows. | 4 | 1h | 1 | 4 |
Setonix | gpu-dev | 20 | 1x 64 | 230 GB | 8 | Exclusive for development and debugging of GPU code and workflows. | - | 4h | - | - |