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 9CAF7329E76 for ; Fri, 15 Oct 2004 22:27:52 +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 73448-10 for ; Fri, 15 Oct 2004 21:27:33 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1350F32A750 for ; Fri, 15 Oct 2004 22:27:34 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9FLRUKS026452; Fri, 15 Oct 2004 17:27:30 -0400 (EDT) To: josh@agliodbs.com Cc: pgsql-performance@postgresql.org, "Simon Riggs" , "Timothy D. Witham" , testperf-general@pgfoundry.org Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... In-reply-to: <200410151338.17277.josh@agliodbs.com> References: <200410151313.13624.josh@agliodbs.com> <26068.1097872442@sss.pgh.pa.us> <200410151338.17277.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Fri, 15 Oct 2004 13:38:17 -0700" Date: Fri, 15 Oct 2004 17:27:29 -0400 Message-ID: <26451.1097875649@sss.pgh.pa.us> From: Tom Lane 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/242 X-Sequence-Number: 8718 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? regards, tom lane