# Compute Specifications (/runners/compute-sizing)



All StarSling runners provide consistent, high-performance compute on 5th Gen AMD EPYC processors. Choose a size based on the compute resources your job requires.

## Specifications

| Label                       | vCPU | Memory | Price per minute |
| --------------------------- | ---- | ------ | ---------------- |
| `starsling-ubuntu-24.04-2`  | 2    | 8 GB   | $0.004           |
| `starsling-ubuntu-24.04`    | 4    | 16 GB  | $0.008           |
| `starsling-ubuntu-24.04-8`  | 8    | 32 GB  | $0.016           |
| `starsling-ubuntu-24.04-16` | 16   | 64 GB  | $0.032           |
| `starsling-ubuntu-24.04-32` | 32   | 128 GB | $0.064           |
| `starsling-ubuntu-24.04-64` | 64   | 256 GB | $0.128           |

The numeric suffix on each label indicates the vCPU count (e.g. `-8` = 8 vCPU). The label without a suffix is the 4 vCPU default and replaces `ubuntu-latest` and `ubuntu-24.04`.

All sizes run Ubuntu 24.04 on 5th Gen AMD EPYC.

## Performance Characteristics

StarSling runners deliver excellent performance for most CI workloads:

* **Web Applications (React, Next.js, Vue)**: Fast installs and builds
* **Backend Services (Go, Rust, Java)**: Efficient parallel compilation
* **Test Suites**: Parallel test execution

Larger sizes (8 vCPU and above) are well-suited for monorepo builds, large test matrices, and compilation-heavy workloads.

## Example Usage

```yaml
runs-on: starsling-ubuntu-24.04
```

For a larger size:

```yaml
runs-on: starsling-ubuntu-24.04-8
```

## Optimization Tips

1. **Cache dependencies**: Use `actions/cache` to avoid repeated downloads
2. **Use matrix builds**: Split tests across multiple runners for parallelism
3. **Right-size your runner**: Larger isn't always better — measure before scaling up

<Cards>
  <Card title="Linux Runners" href="/runners/linux-runners" description="Full runner label reference" />
</Cards>