Coretype sets help avoid queueing of workloads when there is a lack of capacity for a particular core type by indicating the flexibility to run the job on any of the coretypes in a set.
A set can contain a mixture of On Demand Economy (ODE) and On Demand Priority (ODP) coretypes, as well as coretypes from different compute providers.
The image below shows an example coretype set containing Ferrite ODE and Emerald ODE coretypes:
Coretype Launching Order
The order of coretypes in a set, as shown on the hardware settings screen, indicates the order of coretypes and priorities in which the job will try to launch with.
Using the coretype set example above, the job will first try to launch using the Ferrite ODE coretype and if a failure occurs, it will move on to Emerald ODE.
Core Count Transitions
When configuring the hardware settings for a job, the cores per slot value applies to the first coretype in the set. On a coretype transition, and if subsequent coretypes do not have the same available cores per slot, the platform will attempt to match the cores per slot to the closest available core count (either up or down) for the new coretype.
This means a job using a coretype set may not run with the exact core count indicated in job setup.
Note: A coretype set job that started as single node will never transition to a multi-node configuration.
The cost of a coretype set job is dependent on the coretype and the number of cores that the job successfully launches with. The price range displayed next to a coretype set on the hardware selection screen is the set minimum and set maximum of the all the coretypes and their priorities in the set.
When viewing the billing summary on the Company Admin page, the coretype that the job successfully ran with will be displayed.
Custom Coretype Sets
If you'd like to set up a custom coretype set for your organization, please reach out to Rescale Support.