The HPC components of Mahuika (Cray CS400) and Maui (Cray XC50) have been designed to handle fundamentally different workloads:
- Small (1 to a few) core count jobs;
- Small node count jobs (up to 26 nodes (936 cores) in an InfiniBand island);
- Embarrassingly parallel jobs at either the core level or at small node counts;
- Jobs that have poor I/O behaviour (e.g. require high (filesystem) metadata services);
- Require access to huge memory resources on one node.
- Multi-node jobs that demonstrate high performance I/O behaviour (e.g. primarily streaming I/O);
- Jobs that have good scaling properties;
- Embarrassingly parallel multi-node jobs.
Based on the requirements provided by the PI in the NeSI Proposal, the TQP will recommend an Allocation on either Mahuika of Maui. This decision will be informed by:
- The scaling and I/O behaviour of the software application(s) specified in the proposal;
- Availability of HPC resources, and
- For Institution (Collaborator) allocations, the investment by that Collaborator in the NeSI systems.
In many cases scaling information (for "typical" problems) is provided in the NeSI Applications Software catalogue. If the proposed project includes software applications new to NeSI, and the PI does not provide sufficient information for the TQP to assign the project to Maui or Mahuika, the PI will be given a Proposal Development Allocation on both Maui and Mahuika and required to provide fit-for-purpose information in their NeSI Proposal application