From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Don Seiler <don(at)seiler(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Estimating HugePages Requirements? |
Date: | 2021-06-09 17:23:28 |
Message-ID: | CAOBaU_ZHtRhG+MvoT6=HpbMoK=JnsJHBMmxQ-XLSVoh6fFqJHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On Thu, Jun 10, 2021 at 12:42 AM Don Seiler <don(at)seiler(dot)us> wrote:
>
> I'm told other factors contribute to this additional memory requirement, such as max_connections, wal_buffers, etc. I'm wondering if anyone has been able to come up with a reliable method for determining the HugePages requirements for a PG cluster based on the GUC values (that would be known at deployment time).
It also depends on modules like pg_stat_statements and their own
configuration. I think that you can find the required size that your
current configuration will allocate with:
SELECT sum(allocated_size) FROM pg_shmem_allocations ;
From | Date | Subject | |
---|---|---|---|
Next Message | Vijaykumar Jain | 2021-06-09 18:45:40 | Re: Estimating HugePages Requirements? |
Previous Message | Don Seiler | 2021-06-09 16:41:52 | Estimating HugePages Requirements? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-06-09 17:25:59 | Re: Add PortalDrop in exec_execute_message |
Previous Message | Don Seiler | 2021-06-09 16:41:52 | Estimating HugePages Requirements? |