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 3718332A179 for ; Tue, 19 Oct 2004 23:39:57 +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 51510-05 for ; Tue, 19 Oct 2004 22:39:52 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 121CB32A10D for ; Tue, 19 Oct 2004 23:39:54 +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 i9JMdmQ8027698; Tue, 19 Oct 2004 18:39:49 -0400 (EDT) To: josh@agliodbs.com Cc: pgsql-performance@postgresql.org, Manfred Spraul , neilc@samurai.com, markw@osdl.org Subject: Re: futex results with dbt-3 In-reply-to: <200410191459.48080.josh@agliodbs.com> References: <417221B5.1050704@colorfullife.com> <20151.1098222733@sss.pgh.pa.us> <200410191459.48080.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 19 Oct 2004 14:59:48 -0700" Date: Tue, 19 Oct 2004 18:39:48 -0400 Message-ID: <27697.1098225588@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/297 X-Sequence-Number: 8773 Josh Berkus writes: >> The bigger problem here is that the SMP locking bottlenecks we are >> currently seeing are *hardware* issues (AFAICT anyway). > Well, initial results from Gavin/Neil's patch seem to indicate that, while > futexes do not cure the CSStorm bug, they do lessen its effects in terms of > real performance loss. It would be reasonable to expect that futexes would have a somewhat more efficient code path in the case where you have to block (mainly because SysV semaphores have such a heavyweight API, much more complex than we really need). However, the code path that is killing us is the one where you *don't* actually need to block. If we had a proper fix for the problem then the context swap storm itself would go away, and whatever advantage you might be able to measure now for futexes likewise would go away. In other words, I'm not real excited about a wholesale replacement of code in order to speed up a code path that I don't want to be taking in the first place; especially not if that replacement puts a fence between me and working on the code path that I do care about. regards, tom lane