| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Lok P <loknath(dot)73(at)gmail(dot)com> |
| Cc: | dwhite(at)seawardmoon(dot)com, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, Francisco Olarte <folarte(at)peoplecall(dot)com>, haramrae(at)gmail(dot)com, hjp-pgsql(at)hjp(dot)at |
| Subject: | Re: How to do faster DML |
| Date: | 2024-02-12 16:17:41 |
| Message-ID: | CAKAnmmLQJr2ORDMmW-n_7bJ_DijYoKpHjvhATZeSN+048kmHCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 6, 2024 at 12:15 AM Lok P <loknath(dot)73(at)gmail(dot)com> wrote:
> Another thing I noticed the shared_buffer parameters set as 2029684 in
> this instance, which comes to ~21MB and that seems very small for a
> database operating in large scale. And I see we have RAM in the instance
> showing as ~256GB. So thinking of bumping it to something as ~40-50GB.
>
shared_buffers has a unit of 8 kb blocks, so your cluster is set at 15GB,
not 21 MB. Even so, going to 50 would be fine if you have that much RAM.
Hope that will help to some extent. Not sure if there is methods to
> manually, cache some objects(tables/indexes) which were getting used
> frequently by the read queries.
>
That's one of the points of shared_buffers - keep things that are accessed
often in memory. Postgres keeps track of which things are used more often,
so in theory the most frequently used items are removed only when
absolutely necessary.
Cheers,
Greg
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2024-02-12 16:28:41 | Re: How to do faster DML |
| Previous Message | Karsten Hilbert | 2024-02-12 16:07:47 | Re: Safest pgupgrade jump distance |