| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Kenny Bachman <kenny(dot)bachman17(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgresql 14 performance |
| Date: | 2022-08-21 18:57:54 |
| Message-ID: | 3FA5ECDA-A99E-4ACC-B431-54A5BC7FC4D4@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Aug 21, 2022, at 12:55 PM, Kenny Bachman <kenny(dot)bachman17(at)gmail(dot)com> wrote:
>
> How can we explain the cache doesn't work as expected? I mean, I expect more performant the second or third time running because of the cache. However, every time I run it I get the same exec time value.
Take a look at system paging activity, and at pg IO waits. (For the latter, I think you have to enable tracking in postgresql.conf.) Also take a peek at CPU usage--if cache is doing what you expect here, then CPU should go to 100% on one or more cores.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2022-08-21 19:06:46 | Re: Postgresql 14 performance |
| Previous Message | Kenny Bachman | 2022-08-21 18:55:26 | Re: Postgresql 14 performance |