| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Don Seiler <don(at)seiler(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Estimating HugePages Requirements? |
| Date: | 2021-09-03 20:20:59 |
| Message-ID: | 20210903202059.lmtc67pivexfmj3a@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Hi,
On 2021-09-01 15:53:52 +0900, Michael Paquier wrote:
> Hmm. I am not sure about the addition of huge_pages_required, knowing
> that we would have shared_memory_size. I'd rather let the calculation
> part to the user with a scan of /proc/meminfo.
-1. We can easily do better, what do we gain by making the user do this stuff?
Especially because the right value also depends on huge_page_size.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henry Francisco Garcia Cortez | 2021-09-03 20:56:29 | bgwriter and checkpoints |
| Previous Message | Bossart, Nathan | 2021-09-03 17:46:05 | Re: Estimating HugePages Requirements? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-03 20:42:58 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| Previous Message | Andrew Dunstan | 2021-09-03 19:34:24 | Re: Postgres perl module namespace |