From: Scott Carey <scott@richrelevance.com>
To: Christiaan Willemsen <cwillemsen@technocon.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring for maximum memory usage
Date: Thu, 30 Oct 2008 10:37:23 -0700
Message-ID: <a1ec7d000810301037iec3e6c5pec2af7a4e3a0c3af@mail.gmail.com> (raw)
In-Reply-To: <4909E730.5010400@technocon.com>
References: <4909CF9C.80701@technocon.com>
<a1ec7d000810300918w666f705eva3f8fb720dfd7aaf@mail.gmail.com>
<4909E730.5010400@technocon.com>
>
> If you do very large aggregates, you may need even 1GB on work_mem.
> However, a setting that high would require very careful tuning and reduction
> of space used by shared_buffers and the ZFS ARC. Its dangerous since each
> connection with a large aggregate or sort may consume a lot of memory.
>
> Well, some taks may need a lot, but I guess most wil do fine with the
> settings we used right now.
>
> So It looks like I can tune the ARC to use more memory, and also increase
> shared_mem to let postgres cache more tables?
>
I would recommend tuning one upwards, and leaving the other smaller. The
worst case is when they are both similarly sized, it leaves the most
opportunity for duplication of data, and produces the worst feedback on
checkpoint writes.
You may want to compare the performance with:
larger ARC and smaller shared_buffers
vs
smaller ARC and larger shared_buffers
The results will be rather dependent on how you use postgres, the types of
queries you do, and for writes, how you tune checkpoints and such.
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: scott@richrelevance.com, cwillemsen@technocon.com
Subject: Re: Configuring for maximum memory usage
In-Reply-To: <a1ec7d000810301037iec3e6c5pec2af7a4e3a0c3af@mail.gmail.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