[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49fvb28rrm.fsf@segfault.boston.devel.redhat.com>
Date: Thu, 22 Jan 2015 15:49:49 -0500
From: Jeff Moyer <jmoyer@...hat.com>
To: Jens Axboe <axboe@...com>
Cc: Huang Ying <ying.huang@...el.com>, Christoph Hellwig <hch@....de>,
LKML <linux-kernel@...r.kernel.org>, LKP ML <lkp@...org>
Subject: Re: [LKP] [block] 34b48db66e0: +3291.6% iostat.sde.wrqm/s
Jens Axboe <axboe@...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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists