| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Use read streams in pg_visibility |
| Date: | 2024-08-19 06:30:23 |
| Message-ID: | ZsLmf7zXia3psI-U@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 13, 2024 at 03:22:27PM +0300, Nazir Bilal Yavuz wrote:
> Hi,
>
> I am working on using the read stream in pg_visibility. There are two
> places to use it:
>
> 1- collect_visibility_data()
>
> This one is straightforward. I created a read stream object if
> 'include_pd' is true because read I/O is done when 'include_pd' is
> true. There is ~4% timing improvement with this change. I started the
> server with the default settings and created a 6 GB table. Then run
> 100 times pg_visibility() by clearing the OS cache between each run.
> ----------
Mind sharing a script for reproducibility? Except for the drop_caches
part, of course..
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-08-19 06:35:45 | Re: Fsync (flush) all inserted WAL records |
| Previous Message | Thomas Munro | 2024-08-19 06:29:06 | Re: Thread-safe nl_langinfo() and localeconv() |