From: Kevin Grittner <kgrittn@ymail.com>
To: fburgess@radiantblue.com <fburgess@radiantblue.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL 9.3.2 Performance issues
Date: Fri, 24 Jan 2014 12:43:46 -0800 (PST)
Message-ID: <1390596226.15463.YahooMailNeo@web122303.mail.ne1.yahoo.com> (raw)
In-Reply-To: <20140124092332.5a830134ae84016b0174832fdc1a3173.9b700c639c.wbe@email11.secureserver.net>
References: <20140124092332.5a830134ae84016b0174832fdc1a3173.9b700c639c.wbe@email11.secureserver.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
"fburgess@radiantblue.com" <fburgess@radiantblue.com> wrote:
> We have 64GB of Memory on RHEL 6.4
>
> shared_buffers = 8GB
> work_mem = 64MB
> maintenance_work_mem = 1GB
> effective_cache_size = 48GB
> Do these settings look correct for 9.3.2?
Maybe.
What is your max_connections setting?
I find that a good place to start with work_mem is to ignore the
factors you quoted, and to set it somewhere near 25% of machine RAM
divided by max_connections. It might be possible to go up from
there, but monitor closely for peaks of activity which cause enough
memory allocation to flush the OS cache and cause high disk read
rates, killing performance until the cache repopulates. The can
take a while since the high disk read rates slow queries, causing
more of them to compete, leading to higher total work_mem
allocations, and thus preventing recovery from the performance
degradation. In other words, setting this too high leads to
unstable performance. It looks better than a lower setting until
too many users hit Enter at about the same time, causing
performance to collapse for a while.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: kgrittn@ymail.com, fburgess@radiantblue.com
Subject: Re: PostgreSQL 9.3.2 Performance issues
In-Reply-To: <1390596226.15463.YahooMailNeo@web122303.mail.ne1.yahoo.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