Tech riderRev. 20 Sept 2026
Modern FS Benchmark
- 1Runs onLinux, self-hosted
- 2CostsNot stated by the maker
- 3Random I/O testsYes
- 4Sequential testsYes
- 5IOPS measurementYes
- 6Latency measurementYes
- 7Supported platformsLinux
- 8Command-line interfaceYes
7 lines stated Written from the maker's own pages: github.com

Overview
Modern FS Benchmark is ranked #13 of 29 in disk benchmark software on Specifiction. It runs on Linux, Self-hosted.
Compared on disk benchmark software
- Free plan
- Yesgithub.com
- Random I/O tests
- Yesgithub.com
- Sequential tests
- Yesgithub.com
- IOPS measurement
- Yesgithub.com
- Latency measurement
- Yesgithub.com
- Supported platforms
- Linuxgithub.com
- Command-line interface
- Yesgithub.com
Facts
- Purpose
- Modern FS Benchmark continuously benchmarks multi-device copy-on-write filesystems, including btrfs, ZFS, and bcachefs, against ext4 and XFS baselines.github.com · 4 Oct 2026
- Workloads
- Its benchmark phases measure throughput, latency, snapshots, compression, reflinks, degraded operation and rebuild, corruption recovery, and near-full behavior.github.com · 4 Oct 2026
- Results dashboard
- Results are published in a dashboard with per-metric charts, aging curves, run trends, filters, and a sortable table.github.com · 4 Oct 2026
- CI cadence
- GitHub Actions runs benchmarks on every push and on a six-hour schedule using four loop devices backed by sparse files.github.com · 4 Oct 2026
- CI limitation
- Hosted CI devices share one virtual disk, so the project says absolute throughput is meaningless and RAID striping gains are fictional in those runs.github.com · 4 Oct 2026
- Hardware runs
- The scripts can run against real block devices, which are wiped when listed for a benchmark run; devices must be unmounted and existing filesystem signatures require BENCH_WIPE=1.github.com · 4 Oct 2026
- Linux deployment
- The repository provides a Nix flake with a reusable NixOS module and benchmark package for dedicated self-hosted GitHub Actions runners.github.com · 4 Oct 2026
- Security scope
- The corruption test overwrites a raw range on one device, scrubs, and checks one tracked file hash; it is not a whole-filesystem health check.github.com · 4 Oct 2026
- Integrity coverage
- The project describes checksum verification and reconstruction testing for btrfs, ZFS, and bcachefs when redundancy is configured.github.com · 4 Oct 2026
- Methodology limits
- The exact workload recipes and composite summary index are project-specific rather than an industry-standard benchmark.github.com · 4 Oct 2026
- Licensing
- Source code, configuration, workflows, and documentation use Apache License 2.0, while published benchmark datasets use CC BY 4.0.github.com · 4 Oct 2026
- Support
- The maintainer invites issues and pull requests for workload, configuration, methodology, and filesystem suggestions.github.com · 4 Oct 2026
- Sponsor support
- The maintainer says a suitable dedicated server costs approximately €70 per month and accepts financial support through GitHub Sponsors and Ko-fi.github.com · 4 Oct 2026
- Maintainer
- The repository copyright identifies Bartosz Fenski; it does not state a headquarters or founding date.github.com · 4 Oct 2026
- Benchmark coverage
- Its measurements include redundancy layouts, snapshots, compression, encryption, reflinks, fsync latency, degraded operation, rebuilds, corruption recovery, and near-full behavior.github.com · 4 Oct 2026
- Integrations
- The project runs benchmarks in GitHub Actions and provides a reusable NixOS module and benchmark package for self-hosted runners.github.com · 4 Oct 2026
- Local use
- The README documents running the benchmark locally on Linux with loop devices or on real block devices.github.com · 4 Oct 2026
- Security and data integrity
- The corruption phase overwrites a raw range on one device, runs a scrub, and compares a tracked test-file hash; the README cautions that this is not a whole-filesystem health check.github.com · 4 Oct 2026
- Destructive operation
- Real-device runs require unmounted devices, refuse devices with filesystem signatures unless BENCH_WIPE=1 is set, and wipe listed devices.github.com · 4 Oct 2026
- Methodology limitation
- The README says its workload recipes and composite summary index are project-specific rather than an industry-standard benchmark.github.com · 4 Oct 2026
- Project licenses
- The source code, configuration, workflows, and documentation use Apache License 2.0; published benchmark datasets use CC BY 4.0.github.com · 4 Oct 2026
- Hardware support
- The maintainer says a suitable dedicated server currently costs approximately €70 per month, depending on availability and disk configuration, and invites hardware support or sponsorship.github.com · 4 Oct 2026
Best Modern FS Benchmark alternatives
See all 20 All accessCh 01 fio Free planLinuxMac Free to start7.5 All accessCh 02 DaVinci Resolve Free planLinuxMac Free to start7.4 All accessCh 03 Parkdale Free planAndroidMac Free to start7.3 All accessCh 04 Buddi Free planLinuxMac Free to start7.2 All accessCh 05 simple-disk-benchmark Free planLinuxMac Free to start7.0 All accessCh 06 D-Bench Free planWindows Free to start6.9
Where it ranks on Specifiction
- Best Disk Benchmark Software in 2026#13 of 29
Is Modern FS Benchmark yours?
Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.
Sources
- github.com/fenio/modern-fs-benchmark· checked 4 Oct 2026

