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: Thu, 10 Feb 2005 01:55:05 +0100
Message-ID: <420AB0E9.8070808@geizhals.at> (raw)
In-Reply-To: <24848.1107630092@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>
<24848.1107630092@sss.pgh.pa.us>
Tom Lane wrote:
> I'm not completely convinced that you're seeing the same thing,
> but if you're seeing a whole lot of semops then it could well be.
I'm seeing ~280 semops/second with spinlocks enabled and ~80k
semops/second (> 4 mil. for 100 queries) with --disable-spinlocks, which
increases total run time by ~20% only. In both cases, cpu usage stays
around 25%, which is a bit odd.
> [...]You said
> you're testing a quad-processor machine, so it could be that you're
> seeing the same lock contention issues that we've been trying to figure
> out for the past year ...
Are those issues specific to a particular platform (only x86/Linux?) or
is it a problem with SMP systems in general? I guess I'll be following
the current discussion on -hackers closely...
Regards,
Marinos
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: <420AB0E9.8070808@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