[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1212382657.3177.319.camel@ymzhang>
Date: Mon, 02 Jun 2008 12:57:37 +0800
From: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [Bug #10638] sysbench+mysql(oltp, readonly) 30% regression
with 2.6.26-rc1
On Fri, 2008-05-30 at 11:45 +0200, Ingo Molnar wrote:
> Yanmin,
>
> could you please check whether the performance regressions you noticed
> are now fixed in upstream -git? [make sure merge a7f75d3bed28 is
> included]
>
> i believe most of the regressions to 2.6.25 you found should be
> addressed - if not, please let me know which one is still hurting.
Most regressions are fixed.
I tested the latest git tree on a couple of machines. Below results compare with
2.6.25 result except special comments.
1) sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1:
http://bugzilla.kernel.org/show_bug.cgi?id=10638
It's fixed completely.
2) volanoMark regression with kernel 2.6.26-rc1:
http://bugzilla.kernel.org/show_bug.cgi?id=10634
It's fixed completely.
3) hackbench regression with 2.6.26-rc2 on tulsa machine:
http://bugzilla.kernel.org/show_bug.cgi?id=10761
On 16-thread tulsa machine, hackbench result becomes 34 seconds. 2.6.26-rc2's
result is 40 seconds and 2.6.26-rc1's is 30 seconds. So there is much improvement.
On another Montvale machine(supporting multi-threading,
but I don't turn on it in BIOS), hackbench has the similiar behavior.
4) aim7 regression with 2.6.26-rc1:
With Linus's patch which was accepted into 2.6.26-rc2, most aim7 regression disappeared,
but about 6% regression on 16-core tigerton still existed. If just applying Linus' patch
against 2.6.26-rc1, all regression of aim7 disappeared. So there is something else changed
in 2.6.26-rc2.
I retested aim7 against the latest git tree and all aim7 regression disappeared.
5) Kbuild regression 3%~6% with 2.6.26-rc1:
I run kbuild in a loop of 25 or more. On some machines, the testing script drops page cache
at the begining of every loop, and doesn't drop caches on other machines. The second testing
method result is stable, but the first one's result isn't stable. The regression is about the second
method.
I didn't report it because bisect located 2 groups of patches.
With the latest git, I retested kbuild and all regression with the second method disappears.
--
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