Re: Problems with PG 9.3 - Mailing list pgsql-admin

From Dhruv Shukla
Subject Re: Problems with PG 9.3
Date
Msg-id CAFiWeJAn7+cSvipqoxysDPk2ny5xAEXDCL9y9if3pMEhxFsHnw@mail.gmail.com
Whole thread Raw
In response to Re: Problems with PG 9.3  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: Problems with PG 9.3  (Dhruv Shukla <dhruvshukla82@gmail.com>)
Re: Problems with PG 9.3  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-admin
Kevin,
Currently we have a max connection setting for 1000 connections.

And RAM on server is 384GB RAM.

4 Octa core CPU hyperthreaded so total 64 cores.


-Dhruv


On Mon, Aug 25, 2014 at 10:51 AM, Kevin Grittner <kgrittn@ymail.com> wrote:
Dhruv Shukla <dhruvshukla82@gmail.com> wrote:

> Other informational details about configurations are:

> shared_buffers = 80GB
> temp_buffers = 2GB
> work_mem = 2GB
> maintenance_work_mem = 16GB

Well, at the default max_connections of 100 that could easily
result in the server trying to allocate about 567GB of RAM.  If
your number of connections is more than 100, adjust proportionally
higher.  If the server doesn't have that, you could see extreme
swapping or various other problems as the OS tries to survive.

> effective_cache_size = 130GB

And the planner will be generating plans based on the assumption
that the combination of shared_buffers and the OS cache will have
this much RAM available for caching, so if you have max_connections
= 100 this configuration would only make sense on a machine with
RAM of 617GB or more, plus whatever is needed for the OS and
anything besides PostgreSQL that you want to run on the machine.

How much RAM is on the machine (or VM)?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



--
Regards
Dhruv
404-551-2578

pgsql-admin by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: Problems with PG 9.3
Next
From: Dhruv Shukla
Date:
Subject: Re: Problems with PG 9.3