From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Hans Holmberg <Hans.Holmberg@wdc.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>, hch <hch@lst.de>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"jack@suse.com" <jack@suse.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [LSF/MM/BPF TOPIC] A common project for file system performance testing
Date: Thu, 12 Feb 2026 16:42:35 +0000 [thread overview]
Message-ID: <bcedbc03-c307-4de5-9973-94237f05cd85@wdc.com> (raw)
In-Reply-To: <b9f6cd20-8f0f-48d6-9819-e0c915206a3f@wdc.com>
On 2/12/26 2:42 PM, Hans Holmberg wrote:
> Hi all,
>
> I'd like to propose a topic on file system benchmarking:
>
> Can we establish a common project(like xfstests, blktests) for
> measuring file system performance? The idea is to share a common base
> containing peer-reviewed workloads and scripts to run these, collect and
> store results.
>
> Benchmarking is hard hard hard, let's share the burden!
Definitely I'm all in!
> A shared project would remove the need for everyone to cook up their
> own frameworks and help define a set of workloads that the community
> cares about.
>
> Myself, I want to ensure that any optimizations I work on:
>
> 1) Do not introduce regressions in performance elsewhere before I
> submit patches
> 2) Can be reliably reproduced, verified, and regression‑tested by the
> community
>
> The focus, I think, would first be on synthetic workloads (e.g. fio)
> but it could expanded to running application and database workloads
> (e.g. RocksDB).
>
> The fsperf[1] project is a python-based implementation for file system
> benchmarking that we can use as a base for the discussion.
> There are probably others out there as well.
>
> [1] https://github.com/josefbacik/fsperf
I was about to mention Josef's fsperf project. We also used to have some
sort of a dashboard for fsperf results for BTRFS, but that vanished
together with Josef.
A common dashboard with per workload statistics for different
filesystems would be a great thing to have, but for that to work, we'd
need different hardware and probably the vendors of said hardware to buy
in into it.
For developers it would be a benefit to see eventual regressions and
overall weak points, for users it would be a nice tool to see what FS to
pick for what workload.
BUT someone has to do the job setting everything up and maintaining it.
Byte,
Johannes
next prev parent reply other threads:[~2026-02-12 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 13:42 [LSF/MM/BPF TOPIC] A common project for file system performance testing Hans Holmberg
2026-02-12 14:31 ` Daniel Wagner
2026-02-13 11:50 ` Shinichiro Kawasaki
2026-02-12 16:42 ` Johannes Thumshirn [this message]
2026-02-12 17:32 ` Josef Bacik
2026-02-12 17:37 ` [Lsf-pc] " Amir Goldstein
2026-02-12 19:03 ` Josef Bacik
2026-02-13 9:13 ` Hans Holmberg
2026-02-13 6:59 ` Johannes Thumshirn
2026-02-16 10:10 ` Jan Kara
2026-02-17 8:13 ` Hans Holmberg
2026-02-18 15:31 ` Theodore Tso
2026-02-20 8:59 ` Hans Holmberg
2026-02-23 13:26 ` Johannes Thumshirn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcedbc03-c307-4de5-9973-94237f05cd85@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=shinichiro.kawasaki@wdc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.