pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Oleg Bartunov <oleg@sai.msu.su>
To: Kris Kiger <kris@musicrebellion.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: tsearch2 poor performance
Date: Mon, 27 Sep 2004 22:45:32 +0400 (MSD)
Message-ID: <Pine.GSO.4.58.0409272243140.14980@ra.sai.msu.su> (raw)
In-Reply-To: <41584E49.5040301@musicrebellion.com>
References: <71E37EF6B7DCC1499CEA0316A2568328DC9DF0@loki.wc.globexplorer.net>
	<4158409E.8060109@musicrebellion.com>
	<Pine.GSO.4.58.0409272040090.14980@ra.sai.msu.su>
	<41584E49.5040301@musicrebellion.com>

On Mon, 27 Sep 2004, Kris Kiger wrote:

> Oleg,
>
>     Thanks for the help on this.
>
>     The query I used to return the 508 number is:
>          SELECT * FROM stat('SELECT vector FROM product') ORDER BY ndoc
> desc, word ;
>
>     Testing says, the more words I use, the faster the query is.  My
> original search word, 'oil', appears in 226,357 documents 233,266 times.
>  As far as distinct words go, 'oil' is middle of the road for
> occurences.  As it is set up now, the best search time I am getting on
> this single word is roughly 22 seconds.

Does this time (22 seconds) is still better than seq. scan (no index)
or standard 'LIKE' ?

>
> Kris
>
> Oleg Bartunov wrote:
>
> >Kris,
> >
> >do you actually have only 508 disctinct words ? Could you try
> >more complex queries, say 2-3 words. Does these queries run faster ?
> >
> >
> >	Oleg
> >On Mon, 27 Sep 2004, Kris Kiger wrote:
> >
> >
> >
> >>Regardless of caching, the queries are still taking 19~20 seconds to run
> >>on the 3,000,000 rows.  I've played with performance tuning and nothing
> >>seems to make much of a difference.  If I am reading that list from stat
> >>correctly, then I am operating on  508 distinct words.  Is this the
> >>performance I should expect from tsearch2?  Or is something still awry?
> >> I'm inclined to think  something else is wrong, after reading some
> >>other people's tsearch performance stats.  Thanks!
> >>
> >>Kris
> >>
> >>
> >>
> >	Regards,
> >		Oleg
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83



view thread (18+ messages)  latest in thread

Message-ID: <Pine.GSO.4.58.0409272243140.14980@ra.sai.msu.su>
Permalink:  ../Pine.GSO.4.58.0409272243140.14980@ra.sai.msu.su/
Also on:    postgresql.org/message-id/Pine.GSO.4.58.0409272243140.14980@ra.sai.msu.su

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: oleg@sai.msu.su, kris@musicrebellion.com
  Subject: Re: tsearch2 poor performance
  In-Reply-To: <Pine.GSO.4.58.0409272243140.14980@ra.sai.msu.su>
  References: <71E37EF6B7DCC1499CEA0316A2568328DC9DF0@loki.wc.globexplorer.net> <4158409E.8060109@musicrebellion.com> <Pine.GSO.4.58.0409272040090.14980@ra.sai.msu.su> <41584E49.5040301@musicrebellion.com> <Pine.GSO.4.58.0409272243140.14980@ra.sai.msu.su>

* 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