Skip to content
SPECIFICTION
Get listed

dperf

github.com

Free plan LinuxSelf-hosted
Visit github.com
Spec score 7.9 #31 of 73 in PC Benchmark Software

What it is

dperf is a Linux command-line utility for benchmarking drives to identify storage bottlenecks and performance outliers. It runs tests on multiple drives simultaneously and ranks them by throughput. Measurements use O_DIRECT to bypass the operating system page cache. Users can configure block size, file size, and concurrent I/O operations per drive. Results report read and write throughput, with verbose mode adding per-drive statistics alongside aggregate totals. The tool supports sequential tests, but not random I/O tests, IOPS measurement, or latency measurement. Its README describes deployment as Kubernetes Jobs, CronJobs, or DaemonSets for storage validation, as well as automated checks in CI/CD pipelines. Temporary space requirements are based on file size multiplied by I/O operations per drive for each drive. dperf requires Linux, a kernel and filesystem supporting direct I/O, and write access to target directories. Prebuilt binaries are listed for amd64, arm64, ppc64le, and s390x. It is free under the GNU Affero General Public License v3.0.

Spec sheet

Purpose
dperf is a drive benchmarking utility for identifying storage bottlenecks and performance outliers across multiple drives.Read 7 Oct 2026 · github.com
Free plan
YesRead 20 Sep 2026 · github.com
Integrations
The README provides Kubernetes deployment examples and describes automated storage performance checks in CI/CD pipelines.Read 7 Oct 2026 · github.com
Support
The README directs users to GitHub Issues and lists MinIO Sales as the contact for enterprise support.Read 7 Oct 2026 · github.com
License
The project is released under the GNU Affero General Public License v3.0.Read 7 Oct 2026 · github.com
Headquarters
Redwood City, California, United StatesRead 28 Sep 2026 · github.com
Founded
2014Read 28 Sep 2026 · github.com
Architectures
Prebuilt Linux binaries are listed for amd64, arm64, ppc64le, and s390x.Read 7 Oct 2026 · github.com
Direct I/O
It uses O_DIRECT to bypass the operating system page cache for drive performance measurements.Read 7 Oct 2026 · github.com
Kubernetes
The README describes deploying dperf as Kubernetes Jobs, CronJobs, or DaemonSets for storage validation.Read 7 Oct 2026 · github.com
Output
It reports read and write throughput, with verbose mode showing per-drive statistics alongside aggregate totals.Read 7 Oct 2026 · github.com
Parallel benchmarks
It benchmarks multiple drives simultaneously and ranks them by throughput.Read 7 Oct 2026 · github.com
System requirements
dperf requires Linux, a kernel with O_DIRECT support, a filesystem supporting direct I/O, and write access to target directories.Read 7 Oct 2026 · github.com
Temporary storage
The documented disk-space requirement is temporary space equal to filesize multiplied by ioperdrive for each drive.Read 7 Oct 2026 · github.com
Workload settings
Users can configure block size, file size, and concurrent I/O operations per drive.Read 7 Oct 2026 · github.com

Plans and prices

dperf Free AGPL-3.0 licensed; Linux drive benchmarking Read 7 Oct 2026 · github.com

Every dperf plan and price →

Strong points and limits

Strong points

  • Benchmarks multiple drives simultaneously
  • Configurable block size, file size, and concurrent I/O
  • Verbose output includes per-drive statistics
  • Free under GNU AGPL v3.0

Limits

  • Linux only
  • Does not measure IOPS or latency
  • Does not support random I/O tests
  • Requires direct-I/O support and write access

Who it suits

It suits administrators and developers validating storage performance on Linux, including in Kubernetes or CI/CD workflows. It is focused on sequential throughput rather than random I/O, IOPS, or latency.

Verdict

dperf offers configurable, parallel sequential throughput measurements with per-drive reporting. Its Linux and direct-I/O requirements, and its lack of random, IOPS, and latency tests, define its scope.

Where Specifiction places it

Alternatives to dperfAll alternatives →