From: Luis Chamberlain <mcgrof@kernel.org>
To: fio@vger.kernel.org
Cc: andrey.o.kudryavtsev@intel.com, Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/2] fio: few enhancements
Date: Tue, 21 Aug 2018 12:08:22 -0700 [thread overview]
Message-ID: <20180821190824.29928-1-mcgrof@kernel.org> (raw)
I've been toying around with fio's output for a bit, mostly because
Intel's fiovisualizer [0] was the first graphing tool I found for fio, even
though gfio exists. The way fiovisualizer works is it reads terse
ouptut, parses that, and plots data. gfio on the other hand is a proper
built-in client, where communication is exchanged between client/server
and the client plots the data.
If you end up using scraper for terse data such as fiovisualizer with
the prospect to scrape data you will end up with different results if
you use a remote server as a backend.
While studying fio code I realized that the way fiovisualizer implements
graphing is perhaps the wrong / least optimal approach, but also that
fio terse output needed a bit of love for client/server relationship to
keep fidelity in terms of the expected output.
These are just two small enhancements which I hope wil make things
clearer.
[0] https://github.com/intel/fiovisualizer
Luis Chamberlain (2):
client: respect terse output on client <--> backend relationship
init: add semantics for all types of backends running
backend.c | 2 ++
client.c | 16 +++++++++++++---
diskutil.c | 2 +-
fio.h | 8 ++++++++
init.c | 1 +
stat.c | 4 +++-
6 files changed, 28 insertions(+), 5 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-21 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 19:08 Luis Chamberlain [this message]
2018-08-21 19:08 ` [PATCH 1/2] client: respect terse output on client <--> backend relationship Luis Chamberlain
2018-08-31 5:43 ` Sitsofe Wheeler
2018-08-21 19:08 ` [PATCH 2/2] init: add semantics for all types of backends running Luis Chamberlain
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=20180821190824.29928-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=andrey.o.kudryavtsev@intel.com \
--cc=fio@vger.kernel.org \
/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.