From: Joshua D. Drake <jd@commandprompt.com>
To: Warner, Gary, Jr <gar@uab.edu>
To: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Big Memory Boxes and pgtune
Date: Fri, 28 Oct 2016 12:33:10 -0700
Message-ID: <44137c5c-2117-f497-7355-12ae06c1b299@commandprompt.com> (raw)
In-Reply-To: <0cfccbc24b9e480a9452bf9ca79e96e4@UABEX4.ad.uab.edu>
References: <0cfccbc24b9e480a9452bf9ca79e96e4@UABEX4.ad.uab.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 10/28/2016 08:44 AM, Warner, Gary, Jr wrote:
> I've recently been blessed to move one of my databases onto a huge IBM P8 computer. Its a power PC architecture with 20 8-way cores (so postgres SHOULD believe there are 160 cores available) and 1 TB of RAM.
>
> I've always done my postgres tuning with a copy of "pgtune" which says in the output:
>
> # WARNING
> # this tool not being optimal
> # for very high memory systems
>
> So . . . what would I want to do differently based on the fact that I have a "very high memory system"?
The most obvious is that you are going to want to have (depending on
PostgreSQL version):
* A very high shared_buffers (in newer releases, it is not uncommon to
have many, many GB of)
* Use that work_mem baby. You have 1TB available? Take your average data
set return, and make work_mem at least that.
* IIRC (and this may be old advice), maintenance_work_mem up to 4GB. As
I recall it won't effectively use more than that but I could be wrong.
Lastly but most importantly, test test test.
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.
--
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: jd@commandprompt.com, gar@uab.edu
Subject: Re: Big Memory Boxes and pgtune
In-Reply-To: <44137c5c-2117-f497-7355-12ae06c1b299@commandprompt.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