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 94DCA8B9FA5 for ; Wed, 9 Feb 2005 19:25:47 +0000 (GMT) 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 32841-10 for ; Wed, 9 Feb 2005 19:25:40 +0000 (GMT) Received: from morework.geizhals.at (home.geizhals.at [213.229.14.34]) by svr1.postgresql.org (Postfix) with ESMTP id E1EA98B9EA8 for ; Wed, 9 Feb 2005 19:25:38 +0000 (GMT) Received: from localhost (morework [127.0.0.1]) by morework.geizhals.at (Postfix) with ESMTP id 702F4DEBAA; Wed, 9 Feb 2005 20:25:35 +0100 (CET) Received: from [10.0.0.33] (mjy.ghoffice [10.0.0.33]) by morework.geizhals.at (Postfix) with ESMTP; Wed, 9 Feb 2005 20:25:35 +0100 (CET) Message-ID: <420A63B0.5020802@geizhals.at> Date: Wed, 09 Feb 2005 20:25:36 +0100 From: "Marinos J. Yannikos" User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Oleg Bartunov , pgsql-performance@postgresql.org Subject: Re: GiST indexes and concurrency (tsearch2) References: <4201AEB1.4000504@geizhals.at> <4202053B.10207@geizhals.at> <4204C3B4.1050209@geizhals.at> <28977.1107632554@sss.pgh.pa.us> In-Reply-To: <28977.1107632554@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 at geizhals.at X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200502/146 X-Sequence-Number: 10475 Tom Lane wrote: > You might try the attached patch (which I just applied to HEAD). > It cuts down the number of acquisitions of the BufMgrLock by merging > adjacent bufmgr calls during a GIST index search. [...] Thanks - I applied it successfully against 8.0.0, but it didn't seem to have a noticeable effect. I'm still seeing more or less exactly 25% CPU usage by postgres processes and identical query times (measured with the Perl script I posted earlier). Regards, Marinos -- Dipl.-Ing. Marinos Yannikos, CEO Preisvergleich Internet Services AG Obere Donaustrasse 63, A-1020 Wien Tel./Fax: (+431) 5811609-52/-55