Re: Sizing PostgreSQL VM server sizing - Mailing list pgsql-general

From Michael Lewis
Subject Re: Sizing PostgreSQL VM server sizing
Date
Msg-id CAHOFxGp06UrukcoVMD=CpT5wD9iuM5WBmzZaLhZMwEqOeOZmPg@mail.gmail.com
Whole thread Raw
In response to Sizing PostgreSQL VM server sizing  (Samarendra Sahoo <sahoo.samarendra@gmail.com>)
List pgsql-general
On Tue, Aug 11, 2020 at 10:19 AM Samarendra Sahoo <sahoo.samarendra@gmail.com> wrote:
Dear all,
We are getting ready to install in production and would like to know what are key considerations and how do we use them to provision VMs for the same?

It is going to be highly dependent on how the database is used. If you have a terabyte of data, but most of it is (almost) never accessed and you have just one process inserting data, vs wanting to support thousands of concurrent users with a mixture of small transaction queries and also huge reporting queries off the same database... You might need 4 core and 16GB of ram, or you might need 48 cores and 512GB of ram with very fast storage. There are not hard and fast rules, or even clear guidelines that I am aware of. If you expect to deal with many users, you will likely want a connection pooler, whether bundled with your software that accesses the database, or something like pgpool or pg bouncer.

pgsql-general by date:

Previous
From: Philip Semanchuk
Date:
Subject: Re: Implement a new data type
Next
From: pinker
Date:
Subject: Re: insert on conflict postgres returning distinction