From: | Tom Kincaid <tomjohnkincaid(at)gmail(dot)com> |
---|---|
To: | Julien Cigar <jcigar(at)ulb(dot)ac(dot)be> |
Cc: | RAMAKRISHNAN KANDASAMY <ramky24(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 9.3.2 Performance tuning for 32 GB server |
Date: | 2014-02-02 23:52:00 |
Message-ID: | CAKPRjUMqxkZ096XQsdD=Dt=zEewzojjHrvcRde5+0CZzPT55iw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, Jan 31, 2014 at 8:55 AM, Julien Cigar <jcigar(at)ulb(dot)ac(dot)be> wrote:
> On Sat, Jan 25, 2014 at 12:02:59PM +0530, RAMAKRISHNAN KANDASAMY wrote:
> > Hi All,
> >
> > I have configured the blow parameters for a 32 GB server . I this
> correct ?
> >
> > shared_buffers = 6GB
>
> going over 2GB probably doesn't help
>
That is true on 32 bit system. On a 64 bit system with 32GB of RAM, there
is a lot of value to be potentially gained by having shared buffers
significantly higher than 2GB.
>
> It's considered as a bad habit to change the cost settings, but I often
> raise the default cpu_tuple_cost to 0.08 (instead of 0.01) too.
>
> > --
> > --Regards
> > RAMAKRISHNAN KANDASAMY
>
> --
> No trees were killed in the creation of this message.
> However, many electrons were terribly inconvenienced.
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
--
Thomas John
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-02-03 16:55:34 | Re: [PERFORM] encouraging index-only scans |
Previous Message | Bruce Momjian | 2014-02-01 03:22:07 | Re: [PERFORM] encouraging index-only scans |