pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Close <narshe@gmail.com>
To: POSTGRES-PERFORMANCE <pgsql-performance@postgresql.org>
Subject: Re: how much mem to give postgres?
Date: Wed, 20 Oct 2004 08:36:49 -0500
Message-ID: <4a0cafe204102006361e372071@mail.gmail.com> (raw)
In-Reply-To: <29976.1098246931@sss.pgh.pa.us>
References: <4a0cafe2041019153133f854e9@mail.gmail.com>
	<29976.1098246931@sss.pgh.pa.us>

On Wed, 20 Oct 2004 00:35:31 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I suspect that fooling with shared_buffers is entirely the wrong tree
> for you to be barking up.  My suggestion is to be looking at individual
> queries that are slow, and seeing how to speed those up.  This might
> involve adding indexes, or tweaking the query source, or adjusting
> planner parameters, or several other things.  EXPLAIN ANALYZE is your
> friend ...
> 
>                         regards, tom lane

Only problem is, a "select count(1)" is taking a long time. Indexes
shouldn't matter with this since it's counting every row, right? The
tables are fairly well indexed also, I could probably add a few more.

If shared_buffers isn't the way to go ( you said 10k is the sweetspot
), then what about the effective_cache_size? I was suggested on the
general list about possibly setting that to 75% of ram.

Thanks.

-Josh



view thread (11+ messages)  latest in thread

Message-ID: <4a0cafe204102006361e372071@mail.gmail.com>
Permalink:  ../4a0cafe204102006361e372071@mail.gmail.com/
Also on:    postgresql.org/message-id/4a0cafe204102006361e372071@mail.gmail.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: narshe@gmail.com
  Subject: Re: how much mem to give postgres?
  In-Reply-To: <4a0cafe204102006361e372071@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