From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mike Galbraith <efault@gmx.de>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1
Date: Thu, 08 May 2008 11:23:42 +0200 [thread overview]
Message-ID: <1210238622.13978.193.camel@twins> (raw)
In-Reply-To: <1210238114.11887.3.camel@marge.simson.net>
On Thu, 2008-05-08 at 11:15 +0200, Mike Galbraith wrote:
> On Thu, 2008-05-08 at 17:01 +0800, Zhang, Yanmin wrote:
> > On Thu, 2008-05-08 at 10:00 +0200, Mike Galbraith wrote:
>
> > > Hm. I was doing some sysbench+postgress(oltp, ro) testing on my little
> > > Q6600 box this morning, and saw a different picture.
>
> > How many cpu are in the Q6600?
>
> 1.
>
> > >
> > > In attached pdf, .bkl refers to Linus' BKL patch, .weight is the weight
> > > fix, both are applied to git.today. The script I used is also attached.
> > With my 8-core stoakley (using mysql):
> > 1) 2.6.25:
> > Number of threads: 6
> > read/write requests: 8025024 (66874.53 per sec.)
> > Number of threads: 8
> > read/write requests: 9132816 (76106.14 per sec.)
> > Number of threads: 10
> > read/write requests: 9244998 (77040.75 per sec.)
> > Number of threads: 12
> > read/write requests: 8994174 (74950.36 per sec.)
> > Number of threads: 14
> > read/write requests: 9051322 (75426.54 per sec.)
> > Number of threads: 16
> > read/write requests: 9015412 (75126.93 per sec.)
> >
> > 2) 2.6.26-rc1:
> > Number of threads: 6
> > read/write requests: 5754056 (47949.87 per sec.)
> > Number of threads: 8
> > read/write requests: 6528480 (54403.29 per sec.)
> > Number of threads: 10
> > read/write requests: 6444690 (53705.16 per sec.)
> > Number of threads: 12
> > read/write requests: 6544258 (54534.23 per sec.)
> > Number of threads: 14
> > read/write requests: 6796650 (56637.65 per sec.)
> > Number of threads: 16
> > read/write requests: 6718110 (55983.18 per sec.)
> >
> > 3) 2.6.26-rc1+weight
> > Number of threads: 16
> > read/write requests: 3219076 (26824.22 per sec.)
> >
> > I'm not sure if more cpu could introduce more contention in this test.
>
> -rc1. Do you have the fix below applied?
Oooh - good catch, that seems to be a post -rc1 merge.
Yes this is required.
> commit a992241de614dd2b7c97a9ba64e28c0e563f19bf
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Mon May 5 23:56:17 2008 +0200
>
> sched: fix normalized sleeper
>
> Normalized sleeper uses calc_delta*() which requires that the rq load is
> already updated, so move account_entity_enqueue() before place_entity()
>
> Tested-by: Frans Pop <elendil@planet.nl>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
> index 89fa32b..1295ddc 100644
> --- a/kernel/sched_fair.c
> +++ b/kernel/sched_fair.c
> @@ -682,6 +682,7 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int wakeup)
> * Update run-time statistics of the 'current'.
> */
> update_curr(cfs_rq);
> + account_entity_enqueue(cfs_rq, se);
>
> if (wakeup) {
> place_entity(cfs_rq, se, 0);
> @@ -692,7 +693,6 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int wakeup)
> check_spread(cfs_rq, se);
> if (se != cfs_rq->curr)
> __enqueue_entity(cfs_rq, se);
> - account_entity_enqueue(cfs_rq, se);
> }
>
> static void update_avg(u64 *avg, u64 sample)
>
>
next prev parent reply other threads:[~2008-05-08 9:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 4:55 sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1 Zhang, Yanmin
2008-05-07 9:16 ` Ingo Molnar
2008-05-07 9:33 ` Zhang, Yanmin
2008-05-07 10:40 ` Ingo Molnar
2008-05-07 16:26 ` Peter Zijlstra
2008-05-08 6:35 ` Zhang, Yanmin
2008-05-08 8:00 ` Mike Galbraith
2008-05-08 8:46 ` Ingo Molnar
2008-05-08 9:25 ` Ingo Molnar
2008-05-08 10:00 ` Mike Galbraith
2008-05-08 9:37 ` Mike Galbraith
2008-05-08 9:01 ` Zhang, Yanmin
2008-05-08 9:13 ` Peter Zijlstra
2008-05-08 9:15 ` Mike Galbraith
2008-05-08 9:22 ` Zhang, Yanmin
2008-05-08 9:23 ` Peter Zijlstra [this message]
2008-05-09 1:16 ` Zhang, Yanmin
2008-05-09 6:51 ` Peter Zijlstra
2008-05-09 7:32 ` Mike Galbraith
2008-05-09 7:50 ` Peter Zijlstra
2008-05-09 7:58 ` Mike Galbraith
2008-05-09 8:02 ` Peter Zijlstra
2008-05-09 8:23 ` Mike Galbraith
2008-05-09 9:47 ` Mike Galbraith
2008-05-09 7:59 ` Mike Galbraith
2008-05-09 8:10 ` Peter Zijlstra
2008-05-09 8:25 ` Mike Galbraith
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=1210238622.13978.193.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.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