[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1253127000.7166.11.camel@laptop>
Date: Wed, 16 Sep 2009 20:50:00 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
tglx@...utronix.de, mingo@...e.hu
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched: Disable wakeup balancing
On Wed, 2009-09-16 at 15:10 +0000, tip-bot for Peter Zijlstra wrote:
> Commit-ID: 182a85f8a119c789610a9d464f4129ded9f3c107
> Gitweb: http://git.kernel.org/tip/182a85f8a119c789610a9d464f4129ded9f3c107
> Author: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> AuthorDate: Wed, 16 Sep 2009 13:24:49 +0200
> Committer: Ingo Molnar <mingo@...e.hu>
> CommitDate: Wed, 16 Sep 2009 16:44:33 +0200
>
> sched: Disable wakeup balancing
>
> Sysbench thinks SD_BALANCE_WAKE is too agressive and kbuild doesn't
> really mind too much, SD_BALANCE_NEWIDLE picks up most of the
> slack.
>
> On a dual socket, quad core, dual thread nehalem system:
>
> sysbench (--num_threads=16):
>
> SD_BALANCE_WAKE-: 13982 tx/s
> SD_BALANCE_WAKE+: 15688 tx/s
I got the + and - confused it seems.. sysbench is faster without
BALANCE_WAKE.
> kbuild (-j16):
>
> SD_BALANCE_WAKE-: 47.648295846 seconds time elapsed ( +- 0.312% )
> SD_BALANCE_WAKE+: 47.608607360 seconds time elapsed ( +- 0.026% )
--
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