From: Midge Brown <midgems@sbcglobal.net>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: settings input for upgrade
Date: Sat, 20 Aug 2011 22:44:58 -0700
Message-ID: <2B26CB3B354F486195B61647B094753F@BERNICE> (raw)
References: <F0ACDCA889994361A34F7459B11094F0@BERNICE>
<CAOR=d=1+YzrjxcEnQj_nJ55qx0KDP3y5BTKHaeGOwH8e5VwuKQ@mail.gmail.com>
Thank you!
----- Original Message -----
From: Scott Marlowe
To: Midge Brown
Cc: pgsql-performance@postgresql.org
Sent: Saturday, August 20, 2011 9:01 PM
Subject: Re: [PERFORM] settings input for upgrade
On Thu, Aug 18, 2011 at 3:55 PM, Midge Brown wrote:
> Here are the changes I made to postgres.conf. The only differences between
> the conf file for DB1 and those for DB2 & 3 are the port and
> effective_cache_size (which I made slightly smaller -- 8 GB instead of 10 --
> for the 2 write-heavy DBs). The 600 max connections are often idle and don't
> get explicitly closed in the application. I'm looking at connection pooling
> as well.
> work_mem = 128MB
I'd lower this unless you are certain that something like 16MB just
isn't gonna get similar performance. Even with mostly connections
idle, 128M is a rather large work_mem. Remember it's per sort, per
connection. It can quickly cause the kernel to dump file cache that
keeps the machine running fast if a couple dozen connections run a
handful of large sorts at once. What happens is that while things run
smooth when there's low to medium load, under high load the machine
will start thrashing trying to allocate too much work_mem and then
just slow to a crawl.
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: midgems@sbcglobal.net, scott.marlowe@gmail.com
Subject: Re: settings input for upgrade
In-Reply-To: <2B26CB3B354F486195B61647B094753F@BERNICE>
* 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