| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Rohan Kadekodi <kadekodirohan(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-admin(at)lists(dot)postgresql(dot)org, gsievers19(at)comcast(dot)net |
| Subject: | Re: Regarding postgreSQL performance on DRAM |
| Date: | 2019-02-21 15:30:53 |
| Message-ID: | f79c8603-2e22-5c71-3817-7583f469b7bd@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 2019-02-20 22:50, Rohan Kadekodi wrote:
> Perf tool shows that there is a non-trivial amount of time spent in
> DropCachedPlan and AllocSetAlloc. Does this hint to some sort of caching
> being done by PostgreSQL, and is there a way to disable this caching?
AllocSetAlloc() is memory allocation, which, well, you need some of. ;-)
DropCachedPlan() has to do with how statements are prepared and
released. You can probably reduce some of that overhead by using
prepared statements consistently. Hard to tell without more details
about your test script. Have you looked at pgbench?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael King | 2019-02-22 11:19:32 | Removing archived wal files on Master |
| Previous Message | Ron | 2019-02-21 14:41:51 | Re: Moving postgres 9.4 databases to new vm hosted datacenter |