Skip site navigation (1) Skip section navigation (2)

Re: 2.6.26 kernel and PostgreSQL

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
Cc: pgsql-performance(at)postgresql(dot)org, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: 2.6.26 kernel and PostgreSQL
Date: 2009-04-13 08:25:46
Message-ID: alpine.GSO.2.01.0904130412420.3754@westnet.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Fri, 10 Apr 2009, Glyn Astill wrote:

> So it was only for connections over a unix socket, but wow; it's still 
> an ongoing issue.

The problem is actually with pgbench when running on a UNIX socket, not 
with the PostgreSQL server itself.  On my tests, the actual database 
server itself seems to work just as well or better on later kernels that 
use the new scheduler than the older scheduler did.

Basically, if all these apply:

1) You are running pgbench
2) You're running a quick statement, such as a simple select, that gives 
>10000TPS or so
3) Connecting via UNIX socket
4) Clients > around 10
5) Linux kernel >=2.6.23 (which means CFS as the scheduler)
6) The CFS features are at their defaults (SCHED_FEAT_SYNC_WAKEUPS is on)

You'll get weird results.  Change any of those and things are still fine.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

pgsql-performance by date

Next:From: Glyn AstillDate: 2009-04-13 11:49:53
Subject: Re: 2.6.26 kernel and PostgreSQL
Previous:From: Scott MarloweDate: 2009-04-12 23:58:00
Subject: Re: Postgres 8.x on Windows Server in production

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group