[GENERAL] RAM, the more the merrier? - Mailing list pgsql-general

From Willy-Bas Loos
Subject [GENERAL] RAM, the more the merrier?
Date
Msg-id CAHnozTjx4rLfsDk-mE3XqZ+90sazn4EZEy80PH7JdBmn8gMYBw@mail.gmail.com
Whole thread Raw
Responses Re: [GENERAL] RAM, the more the merrier?  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
Re: [GENERAL] RAM, the more the merrier?  (Andreas Kretschmer <andreas@a-kretschmer.de>)
Re: [GENERAL] RAM, the more the merrier?  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
Hi,

We have a postgresql database that is now 1.4TB in disksize and slowly growing.
In the past, we've had (read) performance trouble with this database and the solution was to buy a server that can fit the db into memory. It had 0.5 TB of RAM and at the time it could hold all of the data easily.
Those servers are now old and the db has outgrown the RAM and we are doing more reads and writes too (but the problem has not yet returned).

So i am looking into buying new servers. I'm thinking of equipping it with 1TB of RAM and room to expand. So the database will not fit completely, but largely anyway. Also, if we can afford it, it will have SSDs instead of RAID10 SAS spindles.

But I've read that there is some kind of maximum to the shared_buffers, where increasing it would actually decrease performance.
Is 1TB of RAM, or even 2TB always a good thing?
And is there anything special that I should look out for when configuring such a server?
Or would it be much better to buy 2 smaller servers and tie them together somehow? (partitioning, replication, ...)

--
Willy-Bas Loos

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: [GENERAL] PostGreSQL Timeout, auto shutdown and Pkey errors
Next
From: Achilleas Mantzios
Date:
Subject: Re: [GENERAL] RAM, the more the merrier?