- Home
- Disk Benchmark Software
- Modern FS Benchmark
On the recordRead 4 Oct 202622 facts
Modern FS Benchmark
On the record
- Benchmark coverage
- Its measurements include redundancy layouts, snapshots, compression, encryption, reflinks, fsync latency, degraded operation, rebuilds, corruption recovery, and near-full behavior.github.com · read 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 · read 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 · read 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 · read 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 · read 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 · read 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 · read 4 Oct 2026
- Integrity coverage
- The project describes checksum verification and reconstruction testing for btrfs, ZFS, and bcachefs when redundancy is configured.github.com · read 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 · read 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 · read 4 Oct 2026
- Local use
- The README documents running the benchmark locally on Linux with loop devices or on real block devices.github.com · read 4 Oct 2026
- Maintainer
- The repository copyright identifies Bartosz Fenski; it does not state a headquarters or founding date.github.com · read 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 · read 4 Oct 2026
- Methodology limits
- The exact workload recipes and composite summary index are project-specific rather than an industry-standard benchmark.github.com · read 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 · read 4 Oct 2026
- Purpose
- Modern FS Benchmark continuously benchmarks multi-device copy-on-write filesystems, including btrfs, ZFS, and bcachefs, against ext4 and XFS baselines.github.com · read 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 · read 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 · read 4 Oct 2026
