| From: | Alexander Farber <alexander(dot)farber(at)gmail(dot)com> |
|---|---|
| To: | |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Tuning 9.3 for 32 GB RAM |
| Date: | 2013-11-14 15:09:52 |
| Message-ID: | CAADeyWhE=0vvX-zoENPH+XAsr+-0fSAyCpg2TjCp_1YY6oHVGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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).
Regards
Alex
On Thu, Nov 14, 2013 at 4:04 PM, Alexander Farber <
alexander(dot)farber(at)gmail(dot)com> wrote:
> And pgtune is 4 years old...
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dang Minh Huong | 2013-11-14 15:13:31 | Equivalent syntax of PL/SQL using array in PL/pgSQL |
| Previous Message | Alexander Farber | 2013-11-14 15:04:11 | Re: Tuning 9.3 for 32 GB RAM |