[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1347658843.7172.90.camel@twins>
Date: Fri, 14 Sep 2012 23:40:43 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Borislav Petkov <bp@...en8.de>
Cc: Nikolay Ulyanitsky <lystor@...il.com>,
Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org,
Andreas Herrmann <andreas.herrmann3@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: 20% performance drop on PostgreSQL 9.2 from kernel 3.5.3 to
3.6-rc5 on AMD chipsets - bisected
On Fri, 2012-09-14 at 23:27 +0200, Borislav Petkov wrote:
>
> I was able to reproduce it on another box here and did a bisection run.
> It pointed to the commit below.
>
> And yes, reverting that commit fixes the issue here.
Hmm, cute. What kind of machine did you test it on? Nikolay's machines
look to be smallish AMD X6 or ancient Intel c2d (the patch will indeed
have absolutely no effect on a dual core).
I'll see about running pgbench on a bigger Intel tomorrow if Mike
doesn't beat me to it.
The problem the patch is trying to address is not having to scan an
entire package for idle cores on every wakeup now that packages are
getting stupid big.
Regressing Postgres otoh isn't nice either..
Anyway, I guess I'm fine with nixing this patch until we figure out
something smarter..
I'm also curious to know wth postgres does that this patch makes such a
big difference...
--
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