Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Haseeb Khan <khanhaseeb92@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Page File Size Reached Critical Threshold PostgreSQL V13
Date: Thu, 10 Jun 2021 11:41:09 +0500
Message-Id: <9B6997F1-1E68-41BD-9AB1-E7508CCB48B2@gmail.com>
References: <20210610042853.GB16435@telsasoft.com>
Cc: pgsql-performance@lists.postgresql.org
In-Reply-To: <20210610042853.GB16435@telsasoft.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Archived-At: 
 <https://www.postgresql.org/message-id/9B6997F1-1E68-41BD-9AB1-E7508CCB48B2%40gmail.com>
Precedence: bulk

Hi Justin,=20

You mean, So should I request for to increase the System Ram from 32 Gb to 6=
4 Gb and keep the same parameter setting.Is it ?
=20
Br,
Haseeb Ahmad=20
>=20
> On 10-Jun-2021, at 9:28 AM, Justin Pryzby <pryzby@telsasoft.com> wrote:
>=20
> =EF=BB=BFOn Thu, Jun 10, 2021 at 05:45:45AM +0500, Haseeb Khan wrote:
>> We have installed PostgreSQL V13 on window=E2=80=99s server 2016, where w=
e kept the Ram of the Server is 32 GB and disk size is 270 GB.Later we faced=
 some performance issues regarding the database, after deep dive into it we c=
ame up and increased the Shared buffer size to 16 Gb. After the changed I am=
 not sure we are facing that Page file Size reached to critical threshold. C=
urrently the Page File size is 9504MB.
>=20
> Hi,
>=20
> How large is your DB ?  (Or the "active set" of the DB, if parts of it are=

> accessed infrequently).
>=20
> What was the original performance issue that led you to increase shared_bu=
ffers ?
>=20
> You've set shared_buffers to half of your RAM, which may be a "worst case"=

> setting, since everything that's read into shared_buffers must first be re=
ad
> into the OS cache.  So it may be that many blocks are cached twice, rather=
 than
> relying on a smaller shared_buffers only for the "hottest" blocks, and the=

> larger OS cache for everything else.
>=20
> There are exceptions to the guideline - for example, if your DB is 23 GB i=
n
> size, it might make sense to have the entire thing in 24GB OF shared_buffe=
rs.
> But most DB don't need to fit in shared_buffers, and you shouldn't make th=
at a
> goal, unless you can measure a performance benefit.
>=20
> --=20
> Justin