From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pinker <pinker(at)onet(dot)eu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: dirty_ratio & dirty_background_ratio settings with huge memory |
Date: | 2018-03-06 16:55:57 |
Message-ID: | 20180306165557.7xulgrkfrlyt2kpx@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2018-03-06 03:23:29 -0700, pinker wrote:
> Hi,
> I've got cutomer with really huge RAM, now it's:
> total used free shared buffers cached
> Mem: 3102111 3052596 49515 208801 992 2961185
> -/+ buffers/cache: 90418 3011693
> Swap: 8191 1 8190
>
> (free -m)
>
> and before it was twice more (6TB).
>
> and trying to figure out how to set dirty_ratio & dirty_background_ratio
> parameters. Even for normal sized server those default sizes are to high,
> but now would be ridiculously huge, respectively 1,24TB and 300GB.
> I'm thinking about 1 percent for dirty_ratio and not using
> dirty_background_ratio because it's not possible to set it below 1% but to
> set dirty_background_bytes instead to about 1-2GB.
> Maybe someone has got other experience with RAM of this size and those
> settings?
With a halfway modern PG I'd suggest to rather tune postgres settings
that control flushing. That leaves files like temp sorting in memory for
longer, while flushing things controlledly for other sources of
writes. See *_flush_after settings.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2018-03-06 18:11:38 | Re: plpgsql function-parsing |
Previous Message | Achilleas Mantzios | 2018-03-06 16:16:56 | Re: normalizing a float array? |