# Limitations

> This benchmark measures raw block devices with direct I/O (Input/Output). It
> does *not* measure filesystem performance, page-cache effects, or how a given
> application or database uses the disk. Results show what the disk can do under
> synthetic `fio` load, not what an application will see through a filesystem.

## Disclaimer: What This Benchmark Does *Not* Deliver

### Raw Block I/O

### A Single Score

The output has one record per test and does *not* combine them into a single
number. Spare Cores Navigator will publish bandwidth and IOPS (Input/Output
Operations Per Second) at different block sizes, per disk and for each group of
identical disks. The rest of the output, including any headline metric, is not
decided yet.

### Other `fio` I/O Engines

All tests use the `libaio` I/O engine. The image includes `liburing`, but this
benchmark does *not* test the `io_uring` engine.

## Scope Decisions

### Disk Scope

This benchmark focuses on a server type's bundled storage: the disk or disks
provisioned with the server type by default. These can be a locally attached
SSD or HDD (Hard Disk Drive), or network-attached storage. Network storage
attached on demand is out of scope, because its performance is not a property
of the server type.

Results reflect the bundled storage as provisioned with the server type,
regardless of the underlying medium. A result may therefore be bounded by a
constraint outside the drive itself, such as a provider-imposed IOPS or
bandwidth limit on network-attached storage, or the mechanical limits of an
HDD. This benchmark does not attribute results to a specific cause: it reports
performance as measured, and the Navigator publishes those measurements.

The image does *not* detect which disks are bundled. It tests every real block
device that passes
[discovery](https://docs.sparecores.com/images/benchmark-storage/workloads.md#disk-discovery-and-grouping), including any volume
attached on demand, and overwrites it if it can.

### Read-Only Disks

A disk that is in use (the boot disk, for example) is only read, never written.
Its read tests run over the whole disk, on whatever data it already holds,
without a fill, and it skips every write and mixed test. See
[Disk Safety](https://docs.sparecores.com/images/benchmark-storage/usage.md#disk-safety) for how this benchmark decides.

## Design Constraints

### Partial Fill

The sequential fill runs for at most 300 seconds in total
(`SC_STORAGE_FILL_BUDGET_S`), split between groups. A disk that takes longer to
write is only partly filled. On the first production runs, the fill wrote the
following share of each NVMe (Non-Volatile Memory Express) drive:

- GCP (Google Cloud Platform) `c4a-standard-16-lssd`: 26% of each of four
  drives
- OVHcloud `i1-90`: 33% of each of two drives

A disk that is not fully written still has spare area, flash that holds no
data yet, which inflates random-write results. The fill record's
`filled_fraction` shows how much of each disk the fill wrote. Setting
`SC_STORAGE_WS_TARGET_BYTES` limits the fill, and all later tests, to a smaller
region of each disk.

### Destructive Runs

This benchmark overwrites every disk it may write to, and does not
remount the filesystems it unmounts. Run it only on ephemeral servers, never on
production or similar systems. The `SC_STORAGE_UMOUNT=0` setting leaves mounted
disks alone, but disks that are not in use are always overwritten. See
[Disk Safety](https://docs.sparecores.com/images/benchmark-storage/usage.md#disk-safety).

### Time Budget

This benchmark targets an estimated 2400 seconds of tests. When the estimate
exceeds that, it shortens tests and then drops low-priority ones to fit. See
[Run Duration](https://docs.sparecores.com/images/benchmark-storage/usage.md#run-duration) for the order.
