Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Dilip Kumar <dilipbalaut@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2023-10-25T12:28:09Z

Lists: pgsql-hackers

On Fri, Oct 20, 2023 at 9:40 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Sat, Oct 14, 2023 at 9:43 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > This and other results shared by you look promising. Will there be any
> > improvement in workloads related to clog buffer usage?
>
> I did not understand this question can you explain this a bit?
>

I meant to ask about the impact of this patch on accessing transaction
status via TransactionIdGetStatus(). Shouldn't we expect some
improvement in accessing CLOG buffers?

-- 
With Regards,
Amit Kapila.

Commits

Fix zeroing of pg_serial page without SLRU bank lock
- be2f07310063 17.0 landed
Fix misspelled assertions
- 0d3a71d0c8a7 17.0 landed
GUC table: Add description to computed variables
- 30b8d6e4ce11 17.0 landed
Improve performance of subsystems on top of SLRU
- 53c2a97a9266 17.0 landed
Rename SLRU elements in view pg_stat_slru
- bcdfa5f2e2f2 17.0 landed
Use atomic access for SlruShared->latest_page_number
- d172b717c6f4 17.0 landed
Split use of SerialSLRULock, creating SerialControlLock
- 7b745d85b80d 17.0 landed
Index SLRUs by 64-bit integers rather than by 32-bit integers
- 4ed8f0913bfd 17.0 cited
Add a macro templatized hashtable.
- b30d3ea824c5 10.0 cited