From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Joshua Marsh <icub3d@gmail.com>
Cc: Mark Lonsdale <mark.lonsdale@wysdm.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuration settings for 32GB RAM server
Date: Mon, 04 Dec 2006 13:23:04 -0600
Message-ID: <1165260184.14565.349.camel@state.g2switchworks.com> (raw)
In-Reply-To: <38242de90612041057j63672f7qafa6c6059e9901dc@mail.gmail.com>
References: <673ECBB77DA91F47AD4902A5FD73BCE4D5ED15@mail3>
<38242de90612041057j63672f7qafa6c6059e9901dc@mail.gmail.com>
On Mon, 2006-12-04 at 12:57, Joshua Marsh wrote:
>
> On 12/4/06, Mark Lonsdale <mark.lonsdale@wysdm.com> wrote:
> Maintenance_work_mem = 1048576 – Figured Id allocate 1GB for
> this.
>
>
>
> Do you know how often and when you will be creating indexes or
> clustering? We set ours to 2GB because of the performance gains.
> We've also thought about testing it at 4GB. We can do this because we
> know during the middle of the night our server load drops to nearly
> zero. If you know you have windows like that, then I would definitely
> suggest increasing your maintenance_work_mem. It's halved the time
> for io intesive tasks like cluster.
>
Also, remember that most of those settings (work_mem,
maintenance_work_mem) can be changed for an individual session. So, you
can leave work_mem at something conservative, like 8 meg, and for a
session that is going to run at 2am and iterate over billions of rows,
you can throw several gigabytes at it and not worry about that one
setting blowing out all the other processes on the machine.
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: smarlowe@g2switchworks.com, icub3d@gmail.com, mark.lonsdale@wysdm.com
Subject: Re: Configuration settings for 32GB RAM server
In-Reply-To: <1165260184.14565.349.camel@state.g2switchworks.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