Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tudX0-00AM3Q-SR for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Mar 2025 20:27:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tudWz-004lVY-JB for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Mar 2025 20:27:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tudWz-004lVK-8x for pgsql-hackers@lists.postgresql.org; Tue, 18 Mar 2025 20:27:21 +0000 Received: from fout-a6-smtp.messagingengine.com ([103.168.172.149]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tudWx-003ZU5-1S for pgsql-hackers@lists.postgresql.org; Tue, 18 Mar 2025 20:27:20 +0000 Received: from phl-compute-07.internal (phl-compute-07.phl.internal [10.202.2.47]) by mailfout.phl.internal (Postfix) with ESMTP id E6AD81382CB7; Tue, 18 Mar 2025 16:27:18 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-07.internal (MEProxy); Tue, 18 Mar 2025 16:27:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1742329638; x=1742416038; bh=Zjz6HJJUCt HUS/TjGO7ykE+TQq3EBGTFJeHkiePwtpE=; b=XQtvdNm7OqIQAwDQwgD2oDX7bE mdfyl/PQIlM2InnjjIB+ybuA8JNVokd8Gwzf+DjYLHXBUd5W6sZVGF46ODTS6xQ2 1wNMN1vD+6upwDUXYGUQHNrf6KuZJNMvmPYOY3dCbROW7EwXjuHj8ir5vutbKGO2 WFM2abAPJDHgDcW374dtt06bOtQQ+BjqiWz63l3G2W+zLhZU661tHQuH/5ee1c7g Bx9SH7Bao0sajHEG+McaZREZPTdR1/LPvm+2lxHBtqJCWp/uDkhkyz4kiz/hxq9X i+JOW20b+B1xVCa7cgNJFtX1bP0xYY9jT5zTV3jdFvm1IKWMfEIN/7+p+YMQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1742329638; x=1742416038; bh=Zjz6HJJUCtHUS/TjGO7ykE+TQq3EBGTFJeH kiePwtpE=; b=d0aSnEQyD7WFPjNxJnyzzrANmzgnmVoJqYTTU+HCRVfxROfUCtS h6XVhwy6SZjCvXaF+xAPv7P0IRMIhJXUcwD5OiPf6J0wjyUO3QyppIpf8wdeihnr DBw8R6/HjJBwewIm7goJXOcqDWSsIBkEXmXwnqm9bZ0F7BlgU5I78vP84qnrBfrB mNM9o1i9CVDkyQStTd7U+FVffXGSzalm/PUsbWqSUTx4B/zKgXpHsn+BlAxyxR4a 4t7caobcvOsFNbEhQUOK6xvTUvBUwHMKSNyO1MHpTGDzj5Y/Ru4WPouV6iY8JFjh qHVXxvzHpqAwr33L5gQ8t46+jt9mC4DseUg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddugeefgedtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih gvnhhtshculddquddttddmnecujfgurhepfffhvfevuffkfhggtggujgesthdtsfdttddt vdenucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrg iivghlrdguvgeqnecuggftrfgrthhtvghrnhepfeffgfelvdffgedtveelgfdtgefghfdv kefggeetieevjeekteduleevjefhueegnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdruggvpdhnsggp rhgtphhtthhopeefpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehmvghlrghnih gvphhlrghgvghmrghnsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqhhgr tghkvghrsheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhgpdhrtghpthhtohepsg hruhgtvgesmhhomhhjihgrnhdruhhs X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 Mar 2025 16:27:18 -0400 (EDT) Date: Tue, 18 Mar 2025 16:27:18 -0400 From: Andres Freund To: Bruce Momjian Cc: Melanie Plageman , PostgreSQL-development Subject: Re: Increase default maintenance_io_concurrency to 16 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2025-03-18 16:22:45 -0400, Bruce Momjian wrote: > On Tue, Mar 18, 2025 at 04:13:26PM -0400, Andres Freund wrote: > > Hi, > > > > On 2025-03-18 16:08:22 -0400, Bruce Momjian wrote: > > > This commit makes our default random_page_cost = 4 out of line with > > > these new settings (assumes modern SSD/NAS/SAN hardware) and more out of > > > line with reality. > > > > How so? That seems like an independent consideration to me. > > [thread moved to hackers] > > Uh, I think our old random_page_cost and *_io_concurrency assumed > magnetic disks --- now *_io_concurrency assumes more modern hardware and > random_page_cost assumes magnetic. The cost difference between random and non-random IO is actually still reasonably accurate with NVMEs. You can argue that random_page_cost should be 2.5, but that really depends on the specific hardware. Particularly for cloud style networked storage, you could even argue that the difference between sequential and random IO has *grow* given recent changes in PG (io combining in PG 17), as random IOs much more quickly lead to exhausting IOPS quotas. I still don't think adjusting random_page_cost has any meaningful relation to the change at hand. Greetings, Andres Freund