{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Good Tech Companies ","title":"Understanding Why OS RAM and Postgres Buffer Cache Compete","html":"","width":"100%","height":180,"duration":495,"description":"\n This story was originally published on HackerNoon at: https://hackernoon.com/understanding-why-os-ram-and-postgres-buffer-cache-compete.\nLearn how PostgreSQL double buffering wastes RAM, increases latency, and hurts query performance — plus the 25% shared_buffers rule to fix it.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n You can also check exclusive content about #postgresql-double-buffering, #postgresql-shared_buffers, #pg_buffercache-analysis, #postgres-p95-latency, #postgresql-os-page-cache, #postgresql-memory-tuning, #effective_cache_size-tuning, #good-company, and more.\nThis story was written by: @tigerdata. Learn more about this writer by checking @tigerdata's about page,\n and for more stories, please visit hackernoon.com.\nMany PostgreSQL performance issues aren’t caused by too little RAM, but by allocating memory to the wrong layer. Postgres and the OS both cache the same data independently, creating a “double buffering” problem that wastes memory and increases latency. This guide explains how shared_buffers and the OS page cache interact, why the 25% shared_buffers rule matters, how to diagnose cache pressure with pg_buffercache, and when tuning stops helping because the dataset itself has outgrown memory.\n \n ","thumbnail_url":"https://img.transistorcdn.com/HZ9CRzf5js9DK86xzUVMWBRbXYwg4dA8xVXJGVzpL6Y/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xMTNl/MjgwMmI0ZmEzNThj/YmJiOWNiN2UyZmRm/MzY3My5qcGVn.webp","thumbnail_width":300,"thumbnail_height":300}