From: Marinos J. Yannikos <mjy@geizhals.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: pgsql-performance@postgresql.org
Subject: Re: GiST indexes and concurrency (tsearch2)
Date: Wed, 09 Feb 2005 20:25:36 +0100
Message-ID: <420A63B0.5020802@geizhals.at> (raw)
In-Reply-To: <28977.1107632554@sss.pgh.pa.us>
References: <4201AEB1.4000504@geizhals.at>
<Pine.GSO.4.62.0502031255350.20328@ra.sai.msu.su>
<4202053B.10207@geizhals.at>
<Pine.GSO.4.62.0502031514090.20328@ra.sai.msu.su>
<4204C3B4.1050209@geizhals.at>
<28977.1107632554@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mjy@geizhals.at, tgl@sss.pgh.pa.us, oleg@sai.msu.su
Subject: Re: GiST indexes and concurrency (tsearch2)
In-Reply-To: <420A63B0.5020802@geizhals.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox