From: Jens Axboe <axboe@kernel.dk>
To: emery@sgi.com
Cc: fio@vger.kernel.org
Subject: Re: All clients impatient
Date: Wed, 14 Nov 2012 14:31:57 -0700 [thread overview]
Message-ID: <50A40DCD.7010903@kernel.dk> (raw)
In-Reply-To: <201211142130.qAELUrtO29392794@zion.americas.sgi.com>
On 2012-11-14 14:30, emery@sgi.com wrote:
> emery@sgi.com: Jens Axboe <axboe@kernel.dk>
> In message <50A405C4.50100@kernel.dk>, Jens Axboe writes:
>> On 2012-11-14 12:58, Jens Axboe wrote:
>>> Should work without group_reporting as well with the below patch. Can
>>> you confirm?
>>
>> Committed the patch, with a few modifications. So fio git should work
>> for you now, regardless of whether group_reporting=1 is used or not. I
>> suspect you want it on in any case, as you are only interested in the
>> aggregate results for the clients.
>>
>> --
>> Jens Axboe
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe fio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> I will probably run w/o group_reporting=1. I'm interested
> in both the aggregate performance of the cluster filesystem(s), and
> the deviation of the individual threads.
>
> Aggregate performance helps me quickly see whether I'm getting
> the performance I expect from the filesystem or filesystems. W/o that
> feature I might have to whip out a calculator. :-)
>
> Individual thread performance lets me know whether one or
> more tape drives would be bandwidth starved, which can lead to
> excessive tape wear.
Ah I see, so you do care about individual thread numbers. Which is fine!
And at least everything should work now, regardless of whether
group_reporting is set or not.
--
Jens Axboe
next prev parent reply other threads:[~2012-11-14 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 23:23 All clients impatient Scott Emery
2012-11-14 17:42 ` Jens Axboe
2012-11-14 17:54 ` Jens Axboe
2012-11-14 18:10 ` Jens Axboe
2012-11-14 19:09 ` emery
2012-11-14 19:29 ` emery
2012-11-14 19:58 ` Jens Axboe
2012-11-14 20:57 ` Jens Axboe
2012-11-14 21:30 ` emery
2012-11-14 21:31 ` Jens Axboe [this message]
2012-11-14 21:26 ` emery
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=50A40DCD.7010903@kernel.dk \
--to=axboe@kernel.dk \
--cc=emery@sgi.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.