From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: need suggestion on querying big tables |
Date: | 2022-12-06 16:07:41 |
Message-ID: | AF5ECE5E-E6BA-41DD-B644-EB92A870736A@elevated-dev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Dec 6, 2022, at 8:51 AM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>
> https://www.postgresql.org/docs/11/runtime-config-query.html
>
> effective_cache_size is how much RAM a single query gets. "When setting this parameter you should consider both PostgreSQL's shared buffers".
>
> https://www.postgresql.org/docs/11/runtime-config-resource.html
>
> "a reasonable starting value for shared_buffers is 25% of the memory in your system. There are some workloads where even larger settings for shared_buffers are effective, but because PostgreSQL also relies on the operating system cache, it is unlikely that an allocation of more than 40% of RAM to shared_buffers will work better than a smaller amount."
>
> You've set effective_cache_size to 83%, when it should be at most 20%.
effective_cache_size is a hint as to how much RAM is available for the operating system file cache after all other uses are taken into account.
From | Date | Subject | |
---|---|---|---|
Next Message | Samed YILDIRIM | 2022-12-07 00:06:47 | Re: need suggestion on querying big tables |
Previous Message | Ron | 2022-12-06 15:25:47 | Re: need suggestion on querying big tables |