From owner-freebsd-performance@FreeBSD.ORG Tue Apr 10 19:52:01 2007 Return-Path: X-Original-To: performance@FreeBSD.org Delivered-To: freebsd-performance@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 269ED16A409; Tue, 10 Apr 2007 19:52:01 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.freebsd.org (Postfix) with ESMTP id DAB5C13C484; Tue, 10 Apr 2007 19:52:00 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l3AJq02Y000556; Tue, 10 Apr 2007 15:52:00 -0400 (EDT) To: Kris Kennaway In-reply-to: <20070410194508.GA73072@xor.obsecurity.org> References: <20070226002234.GA80974@xor.obsecurity.org> <461B69C0.4060707@paradise.net.nz> <25573.1176215022@sss.pgh.pa.us> <20070410184332.GC44123@xor.obsecurity.org> <28537.1176230816@sss.pgh.pa.us> <20070410194508.GA73072@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Tue, 10 Apr 2007 15:45:08 -0400" Date: Tue, 10 Apr 2007 15:52:00 -0400 Message-ID: <555.1176234720@sss.pgh.pa.us> From: Tom Lane X-Mailman-Approved-At: Tue, 10 Apr 2007 22:59:53 +0000 Cc: performance@FreeBSD.org, current@FreeBSD.org, Mark Kirkwood , pgsql-hackers Subject: Re: [HACKERS] Anyone interested in improving postgresql scaling? X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2007 19:52:01 -0000 Kris Kennaway writes: > On Tue, Apr 10, 2007 at 02:46:56PM -0400, Tom Lane wrote: >> Oh, I'm sure the BSD kernel acts as you describe. But Mark's point is >> that Postgres never has more than one process waiting on any particular >> SysV semaphore, and so the problem doesn't really affect us. > To be clear, some behaviour that postgresql does with sysv semaphores > causes wakeups of many processes at once. i.e. if you have 20 > clients, you will get up to 20 wakeups. I haven't studied the precise > cause of this, but it is empirically true. This is the scaling > problem I described, and it's what mux's patch addresses. [ shrug... ] To the extent that that happens, it's Postgres' own issue, and no amount of kernel rejiggering will change it. But I certainly have no objection to a patch that fixes the kernel behavior ... regards, tom lane