From: Josh Berkus <josh@agliodbs.com>
To: Jack Coates <jack@lyris.com>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: tuning questions
Date: Thu, 4 Dec 2003 13:24:37 -0800
Message-ID: <200312041324.37889.josh@agliodbs.com> (raw)
In-Reply-To: <1070570264.13923.88.camel@cletus.lyris.com>
References: <1070553983.6498.52.camel@cletus.lyris.com>
<200312042027.22223.dev@archonet.com>
<1070570264.13923.88.camel@cletus.lyris.com>
Jack,
> latest changes:
> shared_buffers = 35642
This is fine, it's about 14% of available RAM. Though the way you calculated
it still confuses me. It's not complicated; it should be between 6% and 15%
of available RAM; since you're doing a data-transformation DB, yours should
be toward the high end.
> max_fsm_relations = 1000
> max_fsm_pages = 10000
You want to raise this a whole lot if your data transformations involve large
delete or update batches. I'd suggest running "vacuum analyze verbose"
between steps to see how many dead pages you're accumulating.
> wal_buffers = 64
> sort_mem = 32768
> vacuum_mem = 32768
> effective_cache_size = 10000
This is way the heck too low. it's supposed to be the size of all available
RAM; I'd set it to 2GB*65% as a start.
> IO is active, but hardly saturated. CPU load is hefty though, load
> average is at 4 now.
Unless you're doing huge statistical aggregates (like radar charts), or heavy
numerical calculations-by-query, high CPU and idle I/O usually indicates a
really bad query, like badly mismatched data types on a join or unconstrained
joins or overblown formatting-by-query.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, jack@lyris.com, dev@archonet.com
Subject: Re: tuning questions
In-Reply-To: <200312041324.37889.josh@agliodbs.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