mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	James Bottomley <JBottomley@odin.com>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	Linux SCSI List <linux-scsi@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [lkp-robot] [scsi] 5c279bd9e4: blogbench.read_score -10.0% regression
Date: Thu, 6 Jul 2017 10:54:21 +0800	[thread overview]
Message-ID: <20170706025421.GB5222@yexl-desktop> (raw)
In-Reply-To: <CACVXFVNWpWb0f-tp2r82Juzq3QH2Prw_gzqVY9tySnAQsLg2Kg@mail.gmail.com>

Hi, Ming Lei

On 07/06, Ming Lei wrote:
>Hi Xiaolong,
>
>On Mon, Jul 3, 2017 at 10:57 AM, kernel test robot
><xiaolong.ye@intel.com> wrote:
>>
>> Greeting,
>>
>> FYI, we noticed a -10.0% regression of blogbench.read_score due to commit:
>
>Looks like related with mq scheduler, could you test the following patch to see
>if your issue can be fixed?
>
>https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-linus&id=32825c45ff8f4cce937ab85b030dc693ceb1aa0a
>

Here is the comparison of commit 5c279bd9e4 and 32825c45, it does help recover
performance back.

$ compare -at 5c279bd9e40624f4ab6e688671026d6005b066fa 32825c45ff8f4cce937ab85b030dc693ceb1aa0a
tests: 1
testcase/path_params/tbox_group/run: blogbench/1SSD-ext4-performance/lkp-bdw-de1

5c279bd9e40624f4  32825c45ff8f4cce937ab85b03  
----------------  --------------------------  
         %stddev      change         %stddev
             \          |                \  
    262860              36%     358558        blogbench.read_score
      9913 ±  4%       -33%       6654        blogbench.write_score
  86266452              31%  1.129e+08        blogbench.time.file_system_inputs
     29.89              22%      36.46        blogbench.time.user_time
       214              13%        242        blogbench.time.percent_of_cpu_this_job_got
       620              12%        696        blogbench.time.system_time
  1.11e+08             -29%   79019314        blogbench.time.file_system_outputs
    439016             -69%     135286        blogbench.time.involuntary_context_switches
      0.64              22%       0.78        mpstat.cpu.usr%
      7.02 ±  4%       -47%       3.72        mpstat.cpu.idle%
    237216            1344%    3425183        softirqs.RCU
    430504             376%    2048486        softirqs.TIMER
    188376             211%     586308        softirqs.SCHED
    306478 ± 32%       -99%       4150 ± 36%  softirqs.NET_RX
  86266452              31%  1.129e+08        time.file_system_inputs
     29.89              22%      36.46        time.user_time

Thanks,
Xiaolong

>
>Thanks,
>Ming Lei

  reply	other threads:[~2017-07-06  2:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  2:57 kernel test robot
2017-07-05 23:45 ` Ming Lei
2017-07-06  2:54   ` Ye Xiaolong [this message]
2017-07-06  7:12     ` Ming Lei

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=20170706025421.GB5222@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=JBottomley@odin.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=martin.petersen@oracle.com \
    --cc=tom.leiming@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

all inboxes | Powered by JetHome®