From: Jens Axboe <axboe@kernel.dk>
To: Jon Tango <cheerios123@outlook.com>,
'Andrey Kuzmin' <andrey.v.kuzmin@gmail.com>
Cc: 'Sitsofe Wheeler' <sitsofe@gmail.com>, fio@vger.kernel.org
Subject: Re: Why Seperate Log Files?
Date: Mon, 11 May 2015 12:20:35 -0400 [thread overview]
Message-ID: <5550D6D3.9050803@kernel.dk> (raw)
In-Reply-To: <BLU406-EAS203C4EE266D87AD0F72049E0DB0@phx.gbl>
On 05/10/2015 09:36 PM, Jon Tango wrote:
> When I use fio in 2.1.8 the write_iops_log command creates a singular log file, even with 8 workers. With fio in the latest versions, however, it creates eight separate log files. Is there a way to get fio to generate a log file for all 8 workers, instead of 8 separate files? That is untenable. I had to go back to 2.1.8 to get a useable output. It's not like the data outputs are very friendly anyway, but with one file at least that data can easily be parsed and worked with. With a different file for each worker it is just ridiculous.
> How do we get one output for all workers?
> It would also be nice if we could just get one output with all of the numbers for the different workers combined, but that may be asking a bit much. Just getting them all in a workable file would be nice :)
Lets back this up a bit. Your bug reporting _sucks_. Constructive
criticism - look it up. You were even lazy enough to just reply to an
old, totally unrelated email, instead of starting a new thread.
So lets try this again. I'll even offer you some free hints. Find out
where the change happened, see if there's reasoning there. If not,
suggest a way to improve the situation. Or even just, constructively,
suggest why the current behavior is a problem and offer your opinion on
how it could be improved to make your life easier. Nobody on this list
owes you anything, you need to earn it.
--
Jens Axboe
next prev parent reply other threads:[~2015-05-11 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 1:36 Why Seperate Log Files? Jon Tango
2015-05-11 16:20 ` Jens Axboe [this message]
2015-05-11 20:28 ` Jon Tango
2015-05-11 21:08 ` Jens Axboe
2015-05-11 21:09 ` Jens Axboe
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=5550D6D3.9050803@kernel.dk \
--to=axboe@kernel.dk \
--cc=andrey.v.kuzmin@gmail.com \
--cc=cheerios123@outlook.com \
--cc=fio@vger.kernel.org \
--cc=sitsofe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox