pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marinos Yannikos <mjy@geizhals.at>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: pgsql-performance@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: GiST indexes and concurrency (tsearch2)
Date: Sat, 05 Feb 2005 14:01:40 +0100
Message-ID: <4204C3B4.1050209@geizhals.at> (raw)
In-Reply-To: <Pine.GSO.4.62.0502031514090.20328@ra.sai.msu.su>
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>

Oleg Bartunov schrieb:
> Marinos,
> 
> what if you construct "apachebench & Co" free  script and see if
> the issue still exists. There are could be many issues doesn't
> connected to postgresql and tsearch2.
> 

Some more things I tried:
- data directory on ramdisk (tmpfs) - no effect
- database connections either over Unix domain sockets or TCP - no effect
- CLUSTER on gist index - approx. 20% faster queries, but CPU usage 
still hovers around 25% (75% idle)
- preemptible kernel - no effect

This is really baffling me, it looks like a kernel issue of some sort 
(I'm only guessing though). I found this old posting: 
http://archives.postgresql.org/pgsql-general/2001-12/msg00836.php - is 
this still applicable? I don't see an unusually high number of context 
switches, but the processes seem to be spending some time in 
"semtimedop" (even though the TAS assembly macros are definetely being 
compiled-in).

If you are interested, I can probably provide an account on one of our 
identically configured boxes by Monday afternoon (GMT+1) with the same 
database and benchmarking utility.

Regards,
  Marinos



view thread (17+ messages)  latest in thread

Message-ID: <4204C3B4.1050209@geizhals.at>
Permalink:  ../4204C3B4.1050209@geizhals.at/
Also on:    postgresql.org/message-id/4204C3B4.1050209@geizhals.at

 · 

reply

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, oleg@sai.msu.su, tgl@sss.pgh.pa.us
  Subject: Re: GiST indexes and concurrency (tsearch2)
  In-Reply-To: <4204C3B4.1050209@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