Re: amazon aroura config - seriously overcommited defaults? (May beOff Topic) - Mailing list pgsql-general

From Andres Freund
Subject Re: amazon aroura config - seriously overcommited defaults? (May beOff Topic)
Date
Msg-id 20181208233818.qu5k5bb4mjklzcqw@alap3.anarazel.de
Whole thread Raw
In response to Re: amazon aroura config - seriously overcommited defaults? (May beOff Topic)  (Rob Sargent <robjsargent@gmail.com>)
Responses Re: amazon aroura config - seriously overcommited defaults? (May beOff Topic)  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Re: amazon aroura config - seriously overcommited defaults? (May beOff Topic)  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-general
On 2018-12-08 15:23:19 -0800, Rob Sargent wrote:
> 
> 
> > On Dec 8, 2018, at 3:12 PM, Andres Freund <andres@anarazel.de> wrote:
> > 
> > On 2018-12-08 12:06:23 -0800, Jeremy Schneider wrote:
> >> On RDS PostgreSQL, the default is 25% of your server memory. This seems
> >> to be pretty widely accepted as a good starting point on PostgreSQL.
> > 
> > FWIW, I think it's widely cited, but also bad advice.  25% for a OLTP
> > workload on a 1TB machine with a database size above 25% is a terrible
> > idea.
> > 
> 
> Sorry, could you please expand “database size above 25%”?  25% of what?

Memory available to postgres (i.e. 100% of the server's memory on a
server dedicated to postgres, less if it's shared duty).

Greetings,

Andres Freund


pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: amazon aroura config - seriously overcommited defaults? (May beOff Topic)
Next
From: Jeremy Schneider
Date:
Subject: Re: Transaction Id Space, Freezing and Wraparound