Re: Performance Tuning Document?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)atentus(dot)com>
Cc: Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: Performance Tuning Document?
Date: 2002-03-28 21:37:33
Message-ID: 200203282137.g2SLbXL29147@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera wrote:
> El Mar 28, Bruce Momjian escribio:
>
> > Matthew Kirkwood wrote:
> > > Hi,
> > >
> > > I'm playing with OSDB (http://osdb.sf.net/) and trying to get
> > > the best numbers possible out of it.
>
> > > Any tips and tricks available? Thus far, I have tried:
> >
> > Gererally, I think 1/4 RAM for shared buffers is a good start, and
> > perhaps 2-4% for sort memory.
>
> That 2-4% means 2-4% per backend, or totalled? I don't have your
> experience, but I think that depends heavily on schemas and queries,
> more than shared buffers.

It is per-backend, and sort memory only helps for certain ORDER BY
queries or mergejoins that can't use an index. It is a very hard value
to set and usually is done to improve certain queries you can't fix
another way. However, the default is unusually small so it will work on
all machines so upping it isn't a major problem.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jason Earl 2002-03-28 22:35:16 Re: Why are selects so slow on large tables, even
Previous Message Alvaro Herrera 2002-03-28 21:35:10 Re: Performance Tuning Document?