From: Tomas Vondra <tv@fuzzy.cz>
To: Ogden <lists@darkstatic.com>
Cc: Andy Colson <andy@squeakycode.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning Tips for a new Server
Date: Wed, 17 Aug 2011 17:08:31 +0200
Message-ID: <fa91e97f5c67b2d07729a618ccca4bd7.squirrel@sq.gransy.com> (raw)
In-Reply-To: <FA1A4F38-77AA-4564-8B26-26E9FB490BDF@darkstatic.com>
References: <959BD2FA-0312-458B-BD5F-ED358D2C47ED@darkstatic.com>
<4E4BC51A.2080503@squeakycode.net>
<FA1A4F38-77AA-4564-8B26-26E9FB490BDF@darkstatic.com>
On 17 Srpen 2011, 16:28, Ogden wrote:
> I was wondering what the best parameters would be with my new setup. The
> work_mem obviously will increase as will everything else as it's a 64Gb
> machine as opposed to a 16Gb machine. The configuration I posted was for
> a 16Gb machine but this new one is 64Gb. I needed help in how to jump
> these numbers up.
Well, that really depends on how you come to the current work_mem settings.
If you've decided that with this amount of work_mem the queries run fine
and higher values don't give you better performance (because the amount of
data that needs to be sorted / hashed) fits into the work_mem, then don't
increase it.
But if you've just set it so that the memory is not exhausted, increasing
it may actually help you.
What I think you should review is the amount of shared buffers,
checkpoints and page cache settings (see this for example
http://notemagnet.blogspot.com/2008/08/linux-write-cache-mystery.html).
Tomas
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: tv@fuzzy.cz, lists@darkstatic.com, andy@squeakycode.net
Subject: Re: Tuning Tips for a new Server
In-Reply-To: <fa91e97f5c67b2d07729a618ccca4bd7.squirrel@sq.gransy.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