All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: lkp@lists.01.org
Subject: Re: [aio] 6098b45b32e: 2200.00% xfstests.generic.239.seconds
Date: Mon, 15 Dec 2014 10:57:53 +0800	[thread overview]
Message-ID: <548E4E31.6050405@cn.fujitsu.com> (raw)
In-Reply-To: <1418605329.5745.141.camel@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3163 bytes --]

Hi Huang,
On 12/15/2014 09:02 AM, Huang Ying wrote:

> FYI, we noticed the below changes on
> 
> commit 6098b45b32e6baeacc04790773ced9340601d511 ("aio: block exit_aio() until all context requests are completed")

This patch added a wait step (which is lacked before) for all submitted aio
missions (iocbs) to complete in exit_aio(), so the cost-time increasing is
expected.

Thanks,
Gu

> 
> 
> testbox/testcase/testparams: vm-vp-2G/xfstests/4HDD-btrfs-generic-quick
> 
> 2ff396be602f10b5  6098b45b32e6baeacc04790773  
> ----------------  --------------------------  
>          %stddev     %change         %stddev
>              \          |                \  
>      26352 ±  9%     -13.6%      22774 ±  1%  vmstat.system.cs
>      10342 ±  6%     -12.3%       9066 ±  0%  vmstat.system.in
>         37 ±  4%     -12.1%         32 ±  3%  time.percent_of_cpu_this_job_got
>       1197 ±  2%     -14.2%       1028 ±  0%  vmstat.io.bi
>      18470 ±  2%     -10.1%      16609 ±  1%  vmstat.io.bo
>        157 ±  3%     +13.7%        179 ±  0%  time.elapsed_time
> 
> vm-vp-2G: qemu-system-x86_64 -enable-kvm -cpu Penryn
> Memory: 2G
> 
>                           xfstests.generic.239.seconds
> 
>   30 ++-----------O---------------------------------------------------------+
>      |              O         O            O         O                      |
>   25 ++                O                                                    |
>      |  O O  O O            O    O O  O  O    O O  O                        |
>      |                   O                                                  |
>   20 O+                                                                     |
>      |                                                                      |
>   15 ++                                                                     |
>      |                                                                      |
>   10 ++                                                                     |
>      |                                                                      |
>      |                                                                      |
>    5 ++                                                                     |
>      |                                                                      |
>    0 *+-*-*--*-*--*-*--*-*--*-*--*-*--*--*-*--*-*--*-*--*-*--*-*--*-*--*-*--*
> 
> 
> 	[*] bisect-good sample
> 	[O] bisect-bad  sample
> 
> To reproduce:
> 
> 	apt-get install ruby ruby-oj
> 	git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> 	cd lkp-tests
> 	bin/setup-local job.yaml # the job file attached in this email
> 	bin/run-local   job.yaml
> 
> 
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
> 
> 
> Thanks,
> Fengguang
> 
> 
> 
> 
> _______________________________________________
> LKP mailing list
> LKP(a)linux.intel.com
> 



WARNING: multiple messages have this Message-ID (diff)
From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Huang Ying <ying.huang@linux.intel.com>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [aio] 6098b45b32e: 2200.00% xfstests.generic.239.seconds
Date: Mon, 15 Dec 2014 10:57:53 +0800	[thread overview]
Message-ID: <548E4E31.6050405@cn.fujitsu.com> (raw)
In-Reply-To: <1418605329.5745.141.camel@linux.intel.com>

Hi Huang,
On 12/15/2014 09:02 AM, Huang Ying wrote:

> FYI, we noticed the below changes on
> 
> commit 6098b45b32e6baeacc04790773ced9340601d511 ("aio: block exit_aio() until all context requests are completed")

This patch added a wait step (which is lacked before) for all submitted aio
missions (iocbs) to complete in exit_aio(), so the cost-time increasing is
expected.

Thanks,
Gu

> 
> 
> testbox/testcase/testparams: vm-vp-2G/xfstests/4HDD-btrfs-generic-quick
> 
> 2ff396be602f10b5  6098b45b32e6baeacc04790773  
> ----------------  --------------------------  
>          %stddev     %change         %stddev
>              \          |                \  
>      26352 ±  9%     -13.6%      22774 ±  1%  vmstat.system.cs
>      10342 ±  6%     -12.3%       9066 ±  0%  vmstat.system.in
>         37 ±  4%     -12.1%         32 ±  3%  time.percent_of_cpu_this_job_got
>       1197 ±  2%     -14.2%       1028 ±  0%  vmstat.io.bi
>      18470 ±  2%     -10.1%      16609 ±  1%  vmstat.io.bo
>        157 ±  3%     +13.7%        179 ±  0%  time.elapsed_time
> 
> vm-vp-2G: qemu-system-x86_64 -enable-kvm -cpu Penryn
> Memory: 2G
> 
>                           xfstests.generic.239.seconds
> 
>   30 ++-----------O---------------------------------------------------------+
>      |              O         O            O         O                      |
>   25 ++                O                                                    |
>      |  O O  O O            O    O O  O  O    O O  O                        |
>      |                   O                                                  |
>   20 O+                                                                     |
>      |                                                                      |
>   15 ++                                                                     |
>      |                                                                      |
>   10 ++                                                                     |
>      |                                                                      |
>      |                                                                      |
>    5 ++                                                                     |
>      |                                                                      |
>    0 *+-*-*--*-*--*-*--*-*--*-*--*-*--*--*-*--*-*--*-*--*-*--*-*--*-*--*-*--*
> 
> 
> 	[*] bisect-good sample
> 	[O] bisect-bad  sample
> 
> To reproduce:
> 
> 	apt-get install ruby ruby-oj
> 	git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> 	cd lkp-tests
> 	bin/setup-local job.yaml # the job file attached in this email
> 	bin/run-local   job.yaml
> 
> 
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
> 
> 
> Thanks,
> Fengguang
> 
> 
> 
> 
> _______________________________________________
> LKP mailing list
> LKP@linux.intel.com
> 



  reply	other threads:[~2014-12-15  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  1:02 [aio] 6098b45b32e: 2200.00% xfstests.generic.239.seconds Huang Ying
2014-12-15  1:02 ` [LKP] " Huang Ying
2014-12-15  2:57 ` Gu Zheng [this message]
2014-12-15  2:57   ` Gu Zheng
2014-12-15  2:58 ` Gu Zheng
2014-12-15  2:58   ` [LKP] " Gu Zheng

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=548E4E31.6050405@cn.fujitsu.com \
    --to=guz.fnst@cn.fujitsu.com \
    --cc=lkp@lists.01.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.