pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Chris Kratz <chris.kratz@vistashare.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Tuning
Date: 09 Feb 2005 15:59:50 -0500
Message-ID: <87wtthcuux.fsf@stark.xeocode.com> (raw)
In-Reply-To: <200502091501.31447.chris.kratz@vistashare.com>
References: <200502091501.31447.chris.kratz@vistashare.com>


Chris Kratz <chris.kratz@vistashare.com> writes:

> We continue to tune our individual queries where we can, but it seems we still 
> are waiting on the db a lot in our app.  When we run most queries, top shows 
> the postmaster running at 90%+ constantly during the duration of the request.  
> The disks get touched occasionally, but not often.  Our database on disk is 
> around 2.6G and most of the working set remains cached in memory, hence the 
> few disk accesses.  All this seems to point to the need for faster 
> processors.

I would suggest looking at the top few queries that are taking the most
cumulative time on the processor. It sounds like the queries are doing a ton
of logical i/o on data that's cached in RAM. A few indexes might cut down on
the memory bandwidth needed to churn through all that data.

> Items changed in the postgresql.conf:
> ...
> random_page_cost = 1		# units are one sequential page fetch cost

This makes it nigh impossible for the server from ever making a sequential
scan when an index would suffice. What query made you do this? What plan did
it fix?


-- 
greg




view thread (15+ messages)  latest in thread

Message-ID: <87wtthcuux.fsf@stark.xeocode.com>
Permalink:  ../87wtthcuux.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87wtthcuux.fsf@stark.xeocode.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: gsstark@mit.edu, chris.kratz@vistashare.com
  Subject: Re: Performance Tuning
  In-Reply-To: <87wtthcuux.fsf@stark.xeocode.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