Zum Hauptinhalt springen
This page is not translated yet. Deutsch is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.

Coretype Sets

concept · Reviewed 2026-09-15 GA

Coretype Sets are ordered lists of coretype and priority pairs. When you submit a job, the platform walks the list in order and launches on the first pair with available capacity. If the first choice is unavailable, the job falls through to the next.

Sets help you avoid queue waits when a specific coretype is at capacity, and they let you start on On Demand Economy (ODE) and fall back to On Demand Priority (ODP) to balance cost and reliability.

Rescale Default Coretype Sets, also called Compute Classes, ship with every account and are kept current by Rescale as new hardware arrives. The General Purpose Compute Class is the common default, with Large Memory and Large Disk Compute Classes for specialized workloads. Rescale selects a Compute Class automatically for new workloads based on the workload type. Custom Coretype Sets are available on request from Rescale Support.

You are billed at the rate of the coretype and priority the job actually used. Cores per slot applies to the first coretype in the Set; if the platform transitions to another coretype whose cores per slot differs, it matches the closest available count up or down. On-Demand Reserved (ODR) priority is not available as part of default Coretype Sets, and the order of a Set is fixed when it is created.

A Set is an ordered list. Rescale tries the first priority coretype, then the second, then the third.

Selecting a Set​

Coretype Sets appear on the Hardware Settings step, and the order shown is the order the platform attempts. A Set might start with Emerald at On-Demand Economy and switch to Ferrite at On-Demand Priority if Emerald has no capacity.

  1. Open the job's Hardware Settings step.
  2. Pick a Coretype Set. The tile shows its coretype and priority pairs, and a price range representing the minimum and maximum across its members.
  3. Configure cores and walltime as you would for a single coretype.
  4. Submit the job.

Two behaviours worth knowing before you plan around a Set:

  • A reclaimed ODE run relaunches down the list. If an ODE pair is reclaimed by the cloud provider mid-run, Rescale attempts to relaunch the job on the next pair in the Set.
  • Node topology can change too. Jobs that support multi-node execution can transition between single- and multi-node configurations across a fallback, not just between coretypes.

Sets and Collections are different things​

Both let the platform choose hardware, and they are easy to confuse:

Coretype SetsCoretype Collections
ShapeAn ordered fallback list you move downA single tile with several eligible machines
PriceVaries with the coretype that succeededFixed at the tile price
Core countMay change on fallbackFixed
PriorityCan mix ODE and ODPODP only

A Collection can be a member of a Set. Use a Set when you would rather accept a different coretype, price or core count than wait for capacity; use a Collection when you want one price and one core count with room for the platform to optimise underneath.