LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: VolanoMark performance improvements (was: Re: volanoMark 12% regression with 2.6.25-rc6)
Date: Fri, 21 Mar 2008 15:18:23 +0800	[thread overview]
Message-ID: <1206083903.14496.117.camel@ymzhang> (raw)
In-Reply-To: <1206083694.14496.114.camel@ymzhang>

On Fri, 2008-03-21 at 15:14 +0800, Zhang, Yanmin wrote:
> On Thu, 2008-03-20 at 09:35 +0800, Zhang, Yanmin wrote:
> > On Wed, 2008-03-19 at 14:48 +0100, Ingo Molnar wrote:
> > > i just tried a handful of kernels with VolanoMark on an Intel quad-core 
> > > testbox,
> > How many physical processors does it have?
> > > these numbers are totally reproducible when running them over a long 
> > > time, i only included 6 runs for brevity. (A sidenote: the 
> > > /proc/sys/kernel/compat_sched_yield switch of 0 or 1 has no effect on 
> > > the .25-rc7 results, and it degraded the .24 results by about 35% so i 
> > > kept it off there.)
> I used java-openjdk to test it with 2.6.25-rc5 by switching compat_sched_yield
> to 0/1. The result difference is about 30%.
> 
> vmstat data when compat_sched_yield=0:
> procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
> 85  0      0 7584984  17128  79264    0    0     0     0    2 716494 37 60  3  0  0
> 94  0      0 7585168  17136  79256    0    0     0    64    7 723299 39 57  4  0  0
> 
> 
> vmstat data when compat_sched_yield=0:
Sorry. below data is when compat_sched_yield=1:

> procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
> 369  0      0 7580656  14364  75852    0    0     0     0    4 1013260 42 57  1  0  0
> 335  0      0 7580836  14364  75852    0    0     0     0    1 971081 41 58  1  0  0
> 414  0      0 7580932  14372  75852    0    0     0    64    7 955333 40 58  1  0  0



      reply	other threads:[~2008-03-21  7:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  9:14 volanoMark 12% regression with 2.6.25-rc6 Zhang, Yanmin
2008-03-18 19:58 ` Ingo Molnar
2008-03-18 20:22   ` Peter Zijlstra
     [not found]     ` <1205894373.3215.621.camel@ymzhang>
2008-03-19 14:01       ` Peter Zijlstra
2008-03-19  2:07   ` Zhang, Yanmin
2008-03-19  2:15     ` Ingo Molnar
2008-03-19  3:18       ` Zhang, Yanmin
2008-03-19  3:28         ` Ingo Molnar
     [not found]           ` <1205901807.3215.659.camel@ymzhang>
2008-03-19 13:48             ` VolanoMark performance improvements (was: Re: volanoMark 12% regression with 2.6.25-rc6) Ingo Molnar
2008-03-20  1:35               ` Zhang, Yanmin
2008-03-21  7:14                 ` Zhang, Yanmin
2008-03-21  7:18                   ` Zhang, Yanmin [this message]

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=1206083903.14496.117.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --subject='Re: VolanoMark performance improvements (was: Re: volanoMark 12% regression with 2.6.25-rc6)' \
    /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

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).