Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 9C5BD635157 for ; Tue, 31 Mar 2009 18:36:14 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 46112-06 for ; Tue, 31 Mar 2009 18:36:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 29836634B38 for ; Tue, 31 Mar 2009 18:36:12 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 31 Mar 2009 16:36:09 -0500 Message-Id: <49D2466F.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.3 Date: Tue, 31 Mar 2009 16:35:59 -0500 From: "Kevin Grittner" To: "Greg Smith" , Subject: Re: Strange behavior: pgbench and new Linux kernels References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200903/442 X-Sequence-Number: 33364 >>> On Thu, Apr 17, 2008 at 7:26 PM, Greg Smith wrote: > On this benchmark 2.6.25 is the worst kernel yet: > It seems I have a lot of work ahead of me here > to nail down and report what's going on here. I don't remember seeing a follow-up on this issue from last year. Are there still any particular kernels to avoid based on this? Thanks, -Kevin