Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p5WTY-0006nP-5N for pgsql-performance@arkaria.postgresql.org; Wed, 14 Dec 2022 18:27:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p5WTW-0004sD-PH for pgsql-performance@arkaria.postgresql.org; Wed, 14 Dec 2022 18:27:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p5WTW-0004s3-GE for pgsql-performance@lists.postgresql.org; Wed, 14 Dec 2022 18:27:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p5WTU-0007gs-Bu for pgsql-performance@lists.postgresql.org; Wed, 14 Dec 2022 18:27:25 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2BEIRNCA2784236; Wed, 14 Dec 2022 13:27:23 -0500 From: Tom Lane To: Jordan Hurwich cc: Samed YILDIRIM , pgsql-performance@lists.postgresql.org, Gautam Bellary Subject: Re: Increased iowait and blk_read_time with higher shared_buffers In-reply-to: References: Comments: In-reply-to Jordan Hurwich message dated "Wed, 14 Dec 2022 10:12:16 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2784234.1671042443.1@sss.pgh.pa.us> Date: Wed, 14 Dec 2022 13:27:23 -0500 Message-ID: <2784235.1671042443@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jordan Hurwich writes: > I'm familiar with the article you linked to, and part of my surprise is > that with these 32GB RAM machines we're seeing better performance at 12.5% > (4GB) than the commonly recommended 25% (8GB) of system memory for > shared_buffers. Your notes about disk read stats from Postgres potentially > actually representing blocks read from the OS cache make sense, I just > imagined that Postgres would be better at managing the memory when it was > dedicated to it via shared_buffers than the OS (obviously with some point > of diminishing returns); and I'm still hoping there's some Postgres > configuration change we can make that enables better performance through > improved utilization of shared_buffers at the commonly recommended 25% of > system memory. Keep in mind that 25% was never some kind of golden number. It is a rough rule of thumb that was invented for far smaller machines than what you're talking about here. regards, tom lane