Steven Winfield wrote:
> Just to be clear, are you suggesting (on linux) setting overcommit_memory = 2
> but leaving overcommit_ratio alone, which defaults to 50%?
> I’ve tried setting them to 2 and 0% respectively in the past and it didn’t
> end well…
Yes, vm.overcommit_memory = 2
As for vm.ove
> Disable memory overcommit and set swappiness to 0 on database servers.
Just to be clear, are you suggesting (on linux) setting overcommit_memory = 2
but leaving overcommit_ratio alone, which defaults to 50%?
I’ve tried setting them to 2 and 0% respectively in the past and it didn’t end
well…
On 18/09/18, Laurenz Albe (laurenz.a...@cybertec.at) wrote:
> Rory Campbell-Lange wrote:
> > We are looking to upgrade our current database server infrastructure so
> > that it is suitable for the next 3 years or so.
> >
> > We envisage needing about 800GB of primary database storage in the next
>
Rory Campbell-Lange wrote:
> We are looking to upgrade our current database server infrastructure so
> that it is suitable for the next 3 years or so.
>
> We envisage needing about 800GB of primary database storage in the next
> three years, with 1000 databases in the cluster.
1000 is a lot, but
[I sent this to the performance list a couple of days ago and received
no replies. Apologies for the cross-post]
We are looking to upgrade our current database server infrastructure so
that it is suitable for the next 3 years or so.
Presently we have two physical servers with the same specs:
