| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Don Seiler <don(at)seiler(dot)us>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Estimating HugePages Requirements? |
| Date: | 2021-06-09 19:28:45 |
| Message-ID: | 1429225.1623266925@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Wed, Jun 9, 2021 at 9:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Just try to start the server and see if it complains.
> Well, I have to *stop* the existing one first, most likely, otherwise
> there won't be enough huge pages (or indeed memory) available.
I'm not following. If you have a production server running, its
pg_shmem_allocations total should already be a pretty good guide
to what you need to configure HugePages for. You need to know to
round that up, of course --- but if you aren't building a lot of
slop into the HugePages configuration anyway, you'll get burned
down the road.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-06-09 19:30:52 | Re: Estimating HugePages Requirements? |
| Previous Message | Magnus Hagander | 2021-06-09 19:23:50 | Re: Estimating HugePages Requirements? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-06-09 19:30:52 | Re: Estimating HugePages Requirements? |
| Previous Message | Tom Lane | 2021-06-09 19:25:11 | Re: unnesting multirange data types |