Re: Memory Tuning

If you have a specific query that you're having trouble with, post it and
the table schema and an EXPLAIN of the query when you run it, generally
someone will have some immediate pointers on how to speed things up.. I
don't have time to go through your site looking for the database schema and
such but if you include some specific information in an email to the list
I'd be happy to take a quick look (and I'm sure others would too)..

Good luck!

-Mitch
Software development :
You can have it cheap, fast or working. Choose two.

----- Original Message -----
From: "Bruno Wolff III" <bruno(at)wolff(dot)to>
To: "Mitch Vincent" <mitch(at)venux(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Friday, March 30, 2001 2:01 PM
Subject: Re: Memory Tuning

> On Fri, Mar 30, 2001 at 10:18:56AM -0500,
> Mitch Vincent <mitch(at)venux(dot)net> wrote:
> > If you could post the schema of your tables that you do the query
against
> > and an EXPLAIN of the queries you're doing, perhaps we could further
tune
> > your queries in addition to beefing up the memory usage of the backend..
>
> This is a bit more than I was expecting. People who do this kind of thing
> generally paid lots of money.
>
> However, if you really want, all of the information on queries and schema
> is available at http://wolff.to/area/ . That is the old box which has a
> lot less memory and a much slower processor. The database schema build
> script is available as well as the source to the perl scripts that handle
> the queries. The especially slow (about 20 seconds before rows are
returned
> - reduced to about 1 second on the new box) queries are the full lists of
> people sorted by name or ID (the ID sort isn't as slow).
>
> Almost all of the data is available. However the people data is accessed
> through a view and there is one person whose name is anonymized.
>
> At this point I wasn't as worried about inefficiencies in the queries
> themselves, but rather how to tell the database server and/or linux to
> best use the memory. The data in the database should easily fit into
memory.
>
> >
> > Check this link out too.
> >
http://postgresql.readysetnet.com/devel-corner/docs/user/performance-tips.ht
> > ml
>
> I will look through that site again. I looked at that previously, but not
> specifically looking for efficient use of memory.
>