pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: eleven@ludojad.itpp.pl, "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: High load average with PostgreSQL 7.4.2 on debian/ibm eserver.
Date: Sun, 18 Jul 2004 11:42:36 +0200
Message-ID: <40FA460C.5030108@bigfoot.com> (raw)
In-Reply-To: <20040629155537.GA5465@ludojad.itpp.pl>
References: <20040629155537.GA5465@ludojad.itpp.pl>

eleven@ludojad.itpp.pl wrote:


> Whole config is available here: 
> http://ludojad.itpp.pl/~eleven/pg-high-load.conf

effective_cache_size = 4000	# typically 8KB each
#random_page_cost = 4		# units are one sequential page fetch cost
#cpu_tuple_cost = 0.01		# (same)
#cpu_index_tuple_cost = 0.001	# (same)
#cpu_operator_cost = 0.0025	# (same)


These values are too higher for your hardware, try to execute the
explain analyze for the queries that are running on your box and
repeat it lowering these values, I bet postgres is running seq scan
instead of an index scan.

These are the value that I use for a configuration closer to your:


effective_cache_size = 20000
random_page_cost = 2.0
cpu_tuple_cost = 0.005
cpu_index_tuple_cost = 0.0005
cpu_operator_cost = 0.0025


last question, do you use the autovacuum daemon ?
If no => you have to use it
If yes => did you apply the patch that will not fail with
           big tables like yours ?


if you can post the autovacuum daemon log ( last lines ).



Regards
Gaetano Mendola









view thread (7+ messages)

Message-ID: <40FA460C.5030108@bigfoot.com>
Permalink:  ../40FA460C.5030108@bigfoot.com/
Also on:    postgresql.org/message-id/40FA460C.5030108@bigfoot.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: mendola@bigfoot.com
  Subject: Re: High load average with PostgreSQL 7.4.2 on debian/ibm eserver.
  In-Reply-To: <40FA460C.5030108@bigfoot.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