whatisgithub

What is modern-fs-benchmark?

fenio/modern-fs-benchmark — explained in plain English

Analysis updated 2026-05-18

19PythonAudience · ops devopsComplexity · 5/5Setup · hard

In one sentence

A continuous benchmark suite that tests how btrfs, ZFS, and bcachefs handle snapshots, compression, device failure, and silent data corruption, compared to ext4 and xfs.

Mindmap

mindmap
  root((repo))
    What it does
      Benchmarks CoW filesystems
      Tests snapshots and compression
      Detects silent corruption
    Tech stack
      Python
      btrfs
      ZFS
      bcachefs
    Use cases
      Compare filesystem reliability
      Evaluate degraded disk rebuild
    Audience
      Storage engineers
      Sysadmins

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Compare how btrfs, ZFS, and bcachefs perform under snapshots, compression, and degraded disk scenarios.

USE CASE 2

Check whether a filesystem detects and repairs silently corrupted data.

USE CASE 3

See how write performance changes as snapshots accumulate over time.

USE CASE 4

Evaluate a filesystem's rebuild behavior after simulating a failed storage device.

What is it built with?

PythonbtrfsZFSbcachefsGitHub Actions

How does it compare?

fenio/modern-fs-benchmark16nic/comfyui-agnes-ai6c696e68/gpt_signup_hybrid
Stars191919
LanguagePythonPythonPython
Setup difficultyhardmoderatehard
Complexity5/52/54/5
Audienceops devopsvibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Running the full benchmark matrix requires multiple disks, several out-of-tree kernel modules, and a CI environment.

So what is it?

Modern FS Benchmark is a continuous testing project that measures how well different advanced filesystems handle real world storage tasks, not just raw speed. A filesystem is the system that decides how data gets organized and stored on a disk, and this project focuses on a newer style called copy on write, used by systems named btrfs, ZFS, and bcachefs, comparing them against the more traditional ext4 and xfs filesystems that most computers use by default. Rather than running a single simple speed test, this project checks many specific, realistic scenarios: how a filesystem behaves when it needs to store many small files, how quickly it can create and delete a large number of files in one folder, what happens to write speed as more and more snapshots, which are saved point in time copies of the data, pile up over time, how well compression works, and how a filesystem performs when one of its storage devices fails and needs to be rebuilt. It also deliberately corrupts data behind a filesystem's back to see whether that filesystem notices the damage and can repair it, or whether it silently serves the broken data without warning anyone. The project runs these tests automatically and regularly, then publishes the results as an online dashboard with charts that can be filtered and compared across different filesystems and storage layouts. Every test result also records the exact software versions used, which matters because some of these filesystems, like ZFS and bcachefs, are not built directly into the standard Linux kernel and need to be added separately. The author's central point is that the real question for long term data storage is not which filesystem is fastest, but which one can be trusted to tell the truth about your data, catching and fixing silent corruption rather than serving damaged files without any warning. This is a specialized tool for people who manage servers, storage systems, or personal file archives and want evidence based comparisons before choosing a filesystem, rather than a tool meant for typical end users.

Copy-paste prompts

Prompt 1
Explain what copy on write means and why it matters for these filesystem benchmarks.
Prompt 2
Walk me through what the snapshot aging test in this benchmark measures.
Prompt 3
Help me understand the difference between the encrypted ZFS, bcachefs, and btrfs configurations tested here.
Prompt 4
Explain how the corruption and scrub test works in this benchmark suite.

Frequently asked questions

What is modern-fs-benchmark?

A continuous benchmark suite that tests how btrfs, ZFS, and bcachefs handle snapshots, compression, device failure, and silent data corruption, compared to ext4 and xfs.

What language is modern-fs-benchmark written in?

Mainly Python. The stack also includes Python, btrfs, ZFS.

How hard is modern-fs-benchmark to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is modern-fs-benchmark for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.