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 C938532A4F1 for ; Fri, 15 Oct 2004 22:32:22 +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 76961-02 for ; Fri, 15 Oct 2004 21:32:17 +0000 (GMT) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id D431032A388 for ; Fri, 15 Oct 2004 22:32:17 +0100 (BST) Received: (from markw@localhost) by mail.osdl.org (8.11.6/8.11.6) id i9FLW6X21560; Fri, 15 Oct 2004 14:32:06 -0700 Date: Fri, 15 Oct 2004 14:32:06 -0700 From: Mark Wong To: Tom Lane Cc: josh@agliodbs.com, Simon Riggs , testperf-general@pgfoundry.org, pgsql-performance@postgresql.org Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... Message-ID: <20041015143206.A17724@osdl.org> References: <200410151313.13624.josh@agliodbs.com> <26068.1097872442@sss.pgh.pa.us> <200410151338.17277.josh@agliodbs.com> <26451.1097875649@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: <26451.1097875649@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Fri, Oct 15, 2004 at 05:27:29PM -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/243 X-Sequence-Number: 8719 On Fri, Oct 15, 2004 at 05:27:29PM -0400, Tom Lane wrote: > Josh Berkus writes: > >> I suspect the reason recalc_sigpending_tsk is so high is that the > >> original coding of PG_TRY involved saving and restoring the signal mask, > >> which led to a whole lot of sigsetmask-type kernel calls. Is this test > >> with beta3, or something older? > > > Beta3, *without* Gavin or Neil's Futex patch. > > Hmm, in that case the cost deserves some further investigation. Can we > find out just what that routine does and where it's being called from? > There's a call-graph feature with oprofile as of version 0.8 with the opstack tool, but I'm having a terrible time figuring out why the output isn't doing the graphing part. Otherwise, I'd have that available already... Mark