pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL performance problem -> tuning
Date: 07 Aug 2003 13:59:14 -0500
Message-ID: <1060282754.12221.50.camel@haggis> (raw)
In-Reply-To: <3F328683.7050008@lviv.bank.gov.ua>
References: <Pine.LNX.4.33.0308071017240.18251-100000@css120.ihs.com>
	<3F328683.7050008@lviv.bank.gov.ua>

On Thu, 2003-08-07 at 12:04, Yaroslav Mazurak wrote:
> scott.marlowe wrote:
> 
> > On Thu, 7 Aug 2003, Yaroslav Mazurak wrote:
> 
> >>Shridhar Daithankar wrote:
> 
[snip]
> > My guess is that this is exactly what's happening to you, you're using so 
> > much memory that the machine is running out and slowing down.
> 
> > Drop shared_buffers to 1000 to 4000, sort_mem to 8192 and start over from 
> > there.  Then, increase them each one at a time until there's no increase 
> > in speed, or stop if it starts getting slower and back off.
> 
> > bigger is NOT always better.
> 
> 	Let I want to use all available RAM with PostgreSQL.
> 	Without executing query (PostgreSQL is running) top say now:

You're missing the point.  PostgreSQL is not designed like Oracle,
Sybase, etc.  

They say, "Give me all the RAM; I will cache everything myself."

PostgreSQL says "The kernel programmers have worked very hard on
disk caching.  Why should I duplicate their efforts?"

Thus, give PG only a "little" RAM, and let the OS' disk cache hold
the rest.

-- 
+---------------------------------------------------------------+
| Ron Johnson, Jr.        Home: ron.l.johnson@cox.net           |
| Jefferson, LA  USA                                            |
|                                                               |
| "Man, I'm pretty.  Hoo Hah!"                                  |
|    Johnny Bravo                                               |
+---------------------------------------------------------------+





view thread (24+ messages)  latest in thread

Message-ID: <1060282754.12221.50.camel@haggis>
Permalink:  ../1060282754.12221.50.camel@haggis/
Also on:    postgresql.org/message-id/1060282754.12221.50.camel@haggis

 · 

reply

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-performance@postgresql.org
  Cc: ron.l.johnson@cox.net
  Subject: Re: PostgreSQL performance problem -> tuning
  In-Reply-To: <1060282754.12221.50.camel@haggis>
  References: <Pine.LNX.4.33.0308071017240.18251-100000@css120.ihs.com> <3F328683.7050008@lviv.bank.gov.ua> <1060282754.12221.50.camel@haggis>

* 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