Use atomic access for SlruShared->latest_page_number
Alvaro Herrera <alvherre@alvh.no-ip.org>
Use atomic access for SlruShared->latest_page_number The new concurrency model proposed for slru.c to improve performance does not include any single lock that would coordinate processes doing concurrent reads/writes on SlruShared->latest_page_number. We can instead use atomic reads and writes for that variable. Author: Dilip Kumar <dilipbalaut@gmail.com> Reviewed-by: Andrey M. Borodin <x4mmm@yandex-team.ru> Discussion: https://postgr.es/m/CAFiTN-vzDvNz=ExGXz6gdyjtzGixKSqs0mKHMmaQ8sOSEFZ33A@mail.gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/transam/clog.c | modified | +1 −5 |
| src/backend/access/transam/commit_ts.c | modified | +3 −4 |
| src/backend/access/transam/multixact.c | modified | +17 −11 |
| src/backend/access/transam/slru.c | modified | +28 −11 |
| src/include/access/slru.h | modified | +4 −1 |
Discussion
- SLRU optimization - configurable buffer pool and partitioning the SLRU lock 131 messages · 2023-10-11 → 2024-04-03