From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
Cc: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Increased I/O / Writes |
Date: | 2016-05-17 11:30:14 |
Message-ID: | CACjxUsMB-qNX5px0-Og0M1Z2rMFO3AeoNq6fh9wdswuX-8PphA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 17, 2016 at 12:11 AM, Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> wrote:
> This is my postgresql.conf at the moment:
>
> shared_buffer(51605MB) +
> effective_cache_size(96760MB) +
> work_mem(32MB) +
> max_connections(200)
>
> = 148397.08 MB
You are comparing some very dissimilar settings. effective_cache_size
does not allocate memory, it tells the planner how much cache you have
allocated (i.e., the sum of shared_buffers and the OS cache).
work_mem can be allocated zero to a large number of times per active
query. Every open connection will use some RAM, but the amount is
hard to predict exactly.
You might want to go over this page:
https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
... and then read the documentation of any setting you are thinking of
adjusting.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Yegorov | 2016-05-17 12:25:15 | Re: Ascii Elephant for text based protocols - Final |
Previous Message | Sridhar N Bamandlapally | 2016-05-17 10:24:17 | Re: Connections - Postgres 9.2 |