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 65F9F329E89 for ; Tue, 19 Oct 2004 22:52:29 +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 13797-01 for ; Tue, 19 Oct 2004 21:52:18 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 44F82329E6E for ; Tue, 19 Oct 2004 22:52:19 +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 i9JLqDkc020152; Tue, 19 Oct 2004 17:52:13 -0400 (EDT) To: Manfred Spraul Cc: neilc@samurai.com, markw@osdl.org, pgsql-performance@postgresql.org Subject: Re: futex results with dbt-3 In-reply-to: <417221B5.1050704@colorfullife.com> References: <417221B5.1050704@colorfullife.com> Comments: In-reply-to Manfred Spraul message dated "Sun, 17 Oct 2004 09:39:33 +0200" Date: Tue, 19 Oct 2004 17:52:13 -0400 Message-ID: <20151.1098222733@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/294 X-Sequence-Number: 8770 Manfred Spraul writes: > Has anyone tried to replace the whole lwlock implementation with > pthread_rwlock? At least for Linux with recent glibcs, pthread_rwlock is > implemented with futexes, i.e. we would get a fast lock handling without > os specific hacks. "At least for Linux" does not strike me as equivalent to "without OS-specific hacks". The bigger problem here is that the SMP locking bottlenecks we are currently seeing are *hardware* issues (AFAICT anyway). The only way that futexes can offer a performance win is if they have a smarter way of executing the basic atomic-test-and-set sequence than we do; and if so, we could read their code and adopt that method without having to buy into any large reorganization of our code. regards, tom lane