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 778AFEAE539 for ; Sat, 23 Oct 2004 12:20:40 +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 29319-02 for ; Sat, 23 Oct 2004 11:20:50 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 10039EAE50A for ; Sat, 23 Oct 2004 12:20:37 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i9NBKmJ7030022 for ; Sat, 23 Oct 2004 11:20:48 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i9NApQBV025377 for pgsql-performance@postgresql.org; Sat, 23 Oct 2004 10:51:26 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: futex results with dbt-3 Date: Sat, 23 Oct 2004 12:51:39 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 30 Message-ID: <417A37BB.9050305@bigfoot.com> References: <417221B5.1050704@colorfullife.com> <20151.1098222733@sss.pgh.pa.us> <200410191459.48080.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Josh Berkus User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: <200410191459.48080.josh@agliodbs.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org 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/386 X-Sequence-Number: 8862 Josh Berkus wrote: > Tom, > > >>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. > > > 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. I proposed weeks ago to see how the CSStorm is affected by stick each backend in one processor ( where the process was born ) using the cpu-affinity capability ( kernel 2.6 ), is this proposal completely out of mind ? Regards Gaetano Mendola