From: Josef Bacik <josef@toxicpanda.com>
To: kernel-team@fb.com, fstests@vger.kernel.org, david@fromorbit.com,
tytso@mit.edu
Subject: [PATCH 0/2] Add fio performance tracking to fstests
Date: Tue, 10 Oct 2017 13:21:23 -0400 [thread overview]
Message-ID: <1507656085-17101-1-git-send-email-josef@toxicpanda.com> (raw)
Everybody agrees that a new project for performance testing is not super useful,
and that it would be better to integrate it into something we all already run.
These two patches take what was fsperf and puts it into fstests proper. This
provides better flexibility for test environments, and at least gets us started
towards adding more of these sort of tests into our day to day activities.
The only thing extra to run these tests is the PERF_CONFIGNAME option that must
be specified in order for the perf tests to be run. We need this (or something
like it) to make sure that we compare runs that have similar setups so that we
don't end up failing because we did one run with NVME but the next run with
SATA.
I've only added one of the fio tests from fsperf because I want to make sure
we're all happy with the generic support that I've added. Once these are merged
I'll send the next tests along and rework how we do comparisons so we're
comparing averages of previous runs instead of just whatever the last run was.
Thanks,
Josef
next reply other threads:[~2017-10-10 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 17:21 Josef Bacik [this message]
2017-10-10 17:21 ` [PATCH 1/2] fstests: add fio perf results support Josef Bacik
2017-10-10 17:53 ` Darrick J. Wong
2017-10-10 18:14 ` Josef Bacik
2017-10-10 18:27 ` Darrick J. Wong
2017-10-10 17:21 ` [PATCH 2/2] perf/001: a random write buffered fio perf test Josef Bacik
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=1507656085-17101-1-git-send-email-josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox