| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Warner, Gary, Jr" <gar(at)uab(dot)edu>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Big Memory Boxes and pgtune |
| Date: | 2016-11-02 23:46:47 |
| Message-ID: | bf50d943-d1a3-e87d-a91d-376434481b22@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 10/28/16 2:33 PM, Joshua D. Drake wrote:
> * A very high shared_buffers (in newer releases, it is not uncommon to
> have many, many GB of)
Keep in mind that you might get very poor results if shared_buffers is
large, but not large enough to fit the entire database. In that case
buffer replacement will be *extremely* expensive. Some operations will
use a different buffer replacement strategy, so you might be OK if some
of the database doesn't fit in shared buffers; that will depend a lot on
your access patterns.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-11-02 23:48:23 | Re: no MCV list of tiny table with unique columns |
| Previous Message | Jim Nasby | 2016-11-02 23:43:02 | Re: query slowdown after 9.0 -> 9.4 migration |