Re: Tuning 9.3 for 32 GB RAM

From: Zev Benjamin <zev-pgsql(at)strangersgate(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Tuning 9.3 for 32 GB RAM
Date: 2013-11-14 16:30:33
Message-ID: 5284FAA9.5010608@strangersgate.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/14/2013 10:09 AM, Alexander Farber wrote:
> pgtune has produced the following for my server (the specs:
> http://www.hetzner.de/en/hosting/produkte_rootserver/px60ssd ):
>
> default_statistics_target = 50
> maintenance_work_mem = 1GB
> constraint_exclusion = on
> checkpoint_completion_target = 0.9
> effective_cache_size = 22GB
> work_mem = 192MB
> wal_buffers = 8MB
> checkpoint_segments = 16
> shared_buffers = 7680MB
> max_connections = 80
>
> Is it really okay? Isn't 22GB too high?
> And how does it know that max_connections =80 is enough in my case? (I
> use pgbouncer).

It doesn't. There is a static map between the "type" (the -T option)
pgtune is using and the max_connections value it sets. You should
consider the output of pgtune as a guideline rather than "optimal settings."

Zev

>
> Regards
> Alex
>
>
>
>
>
>
> On Thu, Nov 14, 2013 at 4:04 PM, Alexander Farber
> <alexander(dot)farber(at)gmail(dot)com <mailto:alexander(dot)farber(at)gmail(dot)com>> wrote:
>
> And pgtune is 4 years old...
>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2013-11-14 16:40:27 Re: Mixed locales and date formatting
Previous Message Vincent Veyron 2013-11-14 16:19:05 Mixed locales and date formatting