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 664D93A3AC7 for ; Mon, 25 Oct 2004 18:31:01 +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 79206-05 for ; Mon, 25 Oct 2004 17:30:58 +0000 (GMT) Received: from dbl.q-ag.de (dbl.q-ag.de [213.172.117.3]) by svr1.postgresql.org (Postfix) with ESMTP id BC03D3A415D for ; Mon, 25 Oct 2004 18:30:55 +0100 (BST) Received: from [127.0.0.2] (dbl [127.0.0.1]) by dbl.q-ag.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i9PHUfSL030207; Mon, 25 Oct 2004 19:30:42 +0200 Message-ID: <417D383E.1010807@colorfullife.com> Date: Mon, 25 Oct 2004 19:30:38 +0200 From: Manfred Spraul User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.7.3) Gecko/20040922 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: neilc@samurai.com, markw@osdl.org, pgsql-performance@postgresql.org Subject: Re: futex results with dbt-3 References: <417221B5.1050704@colorfullife.com> <20151.1098222733@sss.pgh.pa.us> <417697A5.1050600@colorfullife.com> <7178.1098292535@sss.pgh.pa.us> <4176A2C1.3070205@colorfullife.com> <21093.1098722706@sss.pgh.pa.us> In-Reply-To: <21093.1098722706@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/472 X-Sequence-Number: 8948 Tom Lane wrote: >It could be that I'm all wet and there is no relationship between the >cache line thrashing and the seemingly excessive BufMgrLock contention. > > Is it important? The fix is identical in both cases: per-bucket locks for the hash table and a buffer aging strategy that doesn't need one global lock that must be acquired for every lookup. -- Manfred