X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9B64632A99B for ; Fri, 15 Oct 2004 22:56:48 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83776-03 for ; Fri, 15 Oct 2004 21:56:45 +0000 (GMT) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id DD67032A920 for ; Fri, 15 Oct 2004 22:56:46 +0100 (BST) Received: (from markw@localhost) by mail.osdl.org (8.11.6/8.11.6) id i9FLuU927102; Fri, 15 Oct 2004 14:56:30 -0700 Date: Fri, 15 Oct 2004 14:56:30 -0700 From: Mark Wong To: Tom Lane Cc: Sean Chittenden , Kevin Brown , pgsql-performance@postgresql.org Subject: Re: mmap (was First set of OSDL Shared Mem scalability results, some wierdness ... Message-ID: <20041015145630.A21918@osdl.org> References: <157f64840410141725162e43b5@mail.gmail.com> <20041015010841.GE665@filer> <0E3BB9CB-1EE6-11D9-A0BB-000A95C705DC@chittenden.org> <20041015133947.A9225@osdl.org> <26542.1097876270@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <26542.1097876270@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Fri, Oct 15, 2004 at 05:37:50PM -0400 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/246 X-Sequence-Number: 8722 On Fri, Oct 15, 2004 at 05:37:50PM -0400, Tom Lane wrote: > Mark Wong writes: > > I know where the do_sigaction is coming from in this particular case. > > Manfred Spraul tracked it to a pair of pgsignal calls in libpq. > > Commenting out those two calls out virtually eliminates do_sigaction from > > the kernel profile for this workload. > > Hmm, I suppose those are the ones associated with suppressing SIGPIPE > during send(). It looks to me like those should go away in 8.0 if you > have compiled with ENABLE_THREAD_SAFETY ... exactly how is PG being > built in the current round of tests? > Ah, yes. Ok. It's not being configured with any options. That'll be easy to rememdy though. I'll get that change made and we can try again. Mark