From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: tsearch2: very slow queries |
Date: | 2005-08-08 07:36:28 |
Message-ID: | Pine.GSO.4.63.0508081128130.10571@ra.sai.msu.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi there,
tsearch2 is our next problem we plan to attack after we have done with
GiST core. Actually, we did some experiments in background and we're sure we
could very greatly improve tsearch2 performance and add a lot of nice
features. Most probably, we'll call for fund raising for this project
as soon as we find out how to reliably transfer money to us.
Oleg
On Sun, 7 Aug 2005, Marc G. Fournier wrote:
> On Sun, 7 Aug 2005, Joshua D. Drake wrote:
>
>> Marc G. Fournier wrote:
>>>
>>> 'k, I'm obviously doing something wrong, since my experiences with sites
>>> like fts.postgresql.org indicate things should be *alot* faster then I'm
>>> getting ...
>>
>> Well the first thing I would ask is are you running 8.0? My testing shows
>> that Tsearch is pretty abysmal if you are not running 8.0. At least with
>> very large tables.
>
> This is one thing I was fearing, especially with the work that Teodor and
> gang have been putting into it for 8.1 :( Unfortunately, we're currently
> stuck with 7.4.6 for this, so that is one thing I'm going to have to take
> into consideration ...
>
>> Considering the number of rows I am not that surprised but I would be
>> curious to know what type of HD you have? Also correct me if I am wrong but
>> gist indexes are typically very large. Do you have enough work_mem/sort_mem
>> to keep them from going to disk?
>
> I'm currently playing in a non-production environment (ie. my desktop
> machine) just to get a feel for things ... our main server for this is a
> proper 4G of RAM, sort_mem bump'd up quite nicely, and file system spread
> over multiple spindles ...
>
> Right now, I'm just playing with / learning the tsearch stuff, so am more
> looking at a 'this is the worst case scenario on my box', and this improves
> things ... not perfect, but anything I can improve here, I know will be
> easier to improve on the production server :)
>
> ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick.FICHE | 2005-08-08 08:14:26 | Re: Getting actual number of rows updated |
Previous Message | CSN | 2005-08-08 07:32:57 | Getting actual number of rows updated |