From: Mike Rylander <mrylander@gmail.com>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Rick Jansen <rick@rockingstone.nl>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tsearch2 performance on big database
Date: Tue, 22 Mar 2005 12:48:06 +0000
Message-ID: <b918cf3d050322044847d3f9e1@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.62.0503221533400.5508@ra.sai.msu.su>
References: <42400F57.3040604@rockingstone.nl>
<Pine.GSO.4.62.0503221533400.5508@ra.sai.msu.su>
On Tue, 22 Mar 2005 15:36:11 +0300 (MSK), Oleg Bartunov <oleg@sai.msu.su> wrote:
> On Tue, 22 Mar 2005, Rick Jansen wrote:
>
> > Hi,
> >
> > I'm looking for a *fast* solution to search thru ~ 4 million records of book
> > descriptions. I've installed PostgreSQL 8.0.1 on a dual opteron server with
> > 8G of memory, running Linux 2.6. I haven't done a lot of tuning on PostgreSQL
> > itself, but here's the settings I have changed so far:
> >
> > shared_buffers = 2000 (anything much bigger says the kernel doesnt allow it,
> > still have to look into that)
>
> use something like
> echo "150000000" > /proc/sys/kernel/shmmax
> to increase shared memory. In your case you could dedicate much more
> memory.
>
> Regards,
> Oleg
And Oleg should know. Unless I'm mistaken, he (co)wrote tsearch2.
Other than shared buffers, I can't imagine what could be causing that
kind of slowness. EXPLAIN ANALYZE, please?
As an example of what I think you *should* be seeing, I have a similar
box (4 procs, but that doesn't matter for one query) and I can search
a column with tens of millions of rows in around a second.
--
Mike Rylander
mrylander@gmail.com
GPLS -- PINES Development
Database Developer
http://open-ils.org
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: mrylander@gmail.com, oleg@sai.msu.su, rick@rockingstone.nl
Subject: Re: Tsearch2 performance on big database
In-Reply-To: <b918cf3d050322044847d3f9e1@mail.gmail.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