VM IaaS
You operate a machine: an OS, a network identity and everything above it, for as long as you keep it.
Marketplace · HPC & batch
Scheduler-backed capacity, bought from the catalogue. The listing describes the queue, the nodes, the GPUs and the job limits; the provider's scheduler runs the work.
Listing
HPC offerings are catalogue products, not raw scheduler access. The provider publishes the constraints; the listing makes them visible before you order.
| Field | What it fixes |
|---|---|
| Queue / partition | which scheduler lane the job enters |
| Node type | CPU class, GPU class, interconnect |
| CPU / GPU counts | per-job or per-allocation limits |
| Wall time | maximum job duration before the queue ends it |
| Region / facility | where the cluster sits |
| Storage | scratch, project or parallel filesystem |
Catalogue
Three illustrative products — example providers, example figures.
HPC
Illustrative exampleExample Provider
Example facility
Allocation-based
HPC
Illustrative exampleExample Provider
Example facility
Allocation-based
HPC
Illustrative exampleExample Provider
Example facility
Per-job pricing
Workloads
Difference
You operate a machine: an OS, a network identity and everything above it, for as long as you keep it.
You submit work into a scheduler: queues, wall time and node classes replace machine ownership, and metering follows the job or allocation.
Full architecture: the HPC on VirtEngine guide covers schedulers, workload patterns and cluster operations; HPC cluster operators covers the provider side; the x/hpc module documents the job marketplace surface.
Continue