From: Kris Kiger <kris@musicrebellion.com>
To: pgsql-admin@postgresql.org
Subject: Re: tsearch2 poor performance
Date: Mon, 27 Sep 2004 11:32:30 -0500
Message-ID: <4158409E.8060109@musicrebellion.com> (raw)
References: <71E37EF6B7DCC1499CEA0316A2568328DC9DF0@loki.wc.globexplorer.net>
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
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: kris@musicrebellion.com
Subject: Re: tsearch2 poor performance
In-Reply-To: <4158409E.8060109@musicrebellion.com>
References: <71E37EF6B7DCC1499CEA0316A2568328DC9DF0@loki.wc.globexplorer.net> <4158409E.8060109@musicrebellion.com>
* 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