From: Josh Berkus <josh@agliodbs.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org
Subject: Re: Strange behavior: pgbench and new Linux kernels
Date: Sat, 04 Apr 2009 11:55:04 -0700
Message-ID: <49D7AD08.5080202@agliodbs.com> (raw)
In-Reply-To: <alpine.GSO.2.01.0904041147540.27286@westnet.com>
References: <Pine.GSO.4.64.0804170230180.26917@westnet.com>
<fd145f7d0804171009h7658d3bbqf099b5c0e9235268@mail.gmail.com>
<Pine.LNX.4.64.0804171840180.20402@aragorn.flymine.org>
<Pine.GSO.4.64.0804172002010.15803@westnet.com>
<49D2466F.EE98.0025.0@wicourts.gov>
<alpine.GSO.2.01.0904041147540.27286@westnet.com>
On 4/4/09 9:07 AM, Greg Smith wrote:
> On Tue, 31 Mar 2009, Kevin Grittner wrote:
>
>>>>> On Thu, Apr 17, 2008 at 7:26 PM, Greg Smith wrote:
>>
>>> On this benchmark 2.6.25 is the worst kernel yet:
>>
>> 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?
>
> I just discovered something really fascinating here. The problem is
> strictly limited to when you're connecting via Unix-domain sockets; use
> TCP/IP instead, and it goes away.
Have you sent this to any Linux kernel engineers? My experience is that
they're fairly responsive to this sort of thing.
--Josh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, gsmith@gregsmith.com, Kevin.Grittner@wicourts.gov
Subject: Re: Strange behavior: pgbench and new Linux kernels
In-Reply-To: <49D7AD08.5080202@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox