linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@fb.com>
Cc: Huang Ying <ying.huang@intel.com>, Christoph Hellwig <hch@lst.de>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [block] 34b48db66e0: +3291.6% iostat.sde.wrqm/s
Date: Thu, 22 Jan 2015 15:49:49 -0500	[thread overview]
Message-ID: <x49fvb28rrm.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <54C1494D.5050507@fb.com> (Jens Axboe's message of "Thu, 22 Jan 2015 12:02:37 -0700")

Jens Axboe <axboe@fb.com> writes:

>> Agreed on all above, but are the actual benchmark numbers included
>> somewhere in all this mess?  I'd like to see if the benchmark numbers
>> improved first, before digging into the guts of which functions are
>> called more or which stats changed.
>
> I deleted the original email, but the latter tables had drive throughput
> rates and it looked higher for the ones I checked on the newer kernel.
> Which the above math would indicate as well, multiplying reqs-per-sec
> and req-size.

Looking back at the original[1], I think I see the throughput numbers for
iozone.  The part that confused me was that each table mixes different
types of data.  I'd much prefer if different data were put in different
tables, along with column headers that stated what was being reported
and the units for the measurements.

Anyway, I find the increased service time troubling, especially this
one:

testbox/testcase/testparams: ivb44/fsmark/performance-1x-1t-1HDD-xfs-4M-60G-NoSync

       544 ?  0%   +1268.9%       7460 ?  0%  iostat.sda.w_await
       544 ?  0%   +1268.5%       7457 ?  0%  iostat.sda.await

I'll add this to my queue of things to look into.

Cheers,
Jeff

[1] https://lkml.org/lkml/2015/1/21/846

  reply	other threads:[~2015-01-22 20:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  1:21 [LKP] [block] 34b48db66e0: +3291.6% iostat.sde.wrqm/s Huang Ying
2015-01-22  5:37 ` Jens Axboe
2015-01-22 17:47   ` Jeff Moyer
2015-01-22 19:02     ` Jens Axboe
2015-01-22 20:49       ` Jeff Moyer [this message]
2015-01-22 20:58         ` Jens Axboe
2015-01-22 21:08           ` Jeff Moyer
2015-01-22 21:12             ` 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=x49fvb28rrm.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).