Re: pgtune + configurations with 9.3 - Mailing list pgsql-performance

From Shaun Thomas
Subject Re: pgtune + configurations with 9.3
Date
Msg-id 0683F5F5A5C7FE419A752A034B4A0B9797DCD287@sswchi5pmbx2.peak6.net
Whole thread Raw
In response to Re[2]: [PERFORM] pgtune + configurations with 9.3  (Alexey Vasiliev <leopard_ne@inbox.ru>)
Responses [PERFORM] pgtune + configurations with 9.3
List pgsql-performance
Alexey,

The issue is that the 1/4 memory suggestion hasn't been a recommendation in quite a while. Now that much larger amounts
ofRAM are readily available, tests have been finding out that more than 8GB of RAM in shared_buffers has diminishing or
evenworse returns. This is true for any version. Further, since PostgreSQL manages its own memory, and the Linux Kernel
alsomanages various caches, there's significant risk of storing the same memory both in shared_buffers, and in file
cache.

There are other tweaks the tool probably needs, but I think this, more than anything else, needs to be updated. Until
PGsolves the issue of double-buffering (which is somewhat in progress since they're somewhat involved with the Linux
kerneldevs) you can actually give it too much memory. 


______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


pgsql-performance by date:

Previous
From: Glyn Astill
Date:
Subject: Re: 9.0 performance degradation with kernel 3.11
Next
From: Alexey Vasiliev
Date:
Subject: [PERFORM] pgtune + configurations with 9.3