Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJTHT-0006rl-OQ for pgsql-performance@arkaria.postgresql.org; Mon, 27 Nov 2017 23:57:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJTHT-0004ZA-8X for pgsql-performance@arkaria.postgresql.org; Mon, 27 Nov 2017 23:57:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eJTHS-0004Yp-R5 for pgsql-performance@lists.postgresql.org; Mon, 27 Nov 2017 23:57:43 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eJTHP-00016t-N5 for pgsql-performance@lists.postgresql.org; Mon, 27 Nov 2017 23:57:42 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 266F420C27; Mon, 27 Nov 2017 18:57:38 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 27 Nov 2017 18:57:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=oyUrrien6CPVT2kgGlFNZfC83Q33W uJsOVrt8VfgI14=; b=lmsqYyDmjlflztrxMTAiEMeipAM/UlUE2pUhkyZOSRKdf GaqX8oqDjfPYtZR/hNhGtkMvXRB+F3ob0fY3H1p2/SLm9Gc81yn/tysZZ1lNO6xM gvYMYmeQzpN0IZt59raUSWVQf8zpoQbg6wipjjwzZUN1G4ZGuA0pK2Bqa1VJenc2 wzb4gvufUin16fw3z3DPPw8AyFAk3QNnJgAtaTIqonFzRo5qY4yTkZCWUR3qY2+b haqvVgpll/h+Mceq6/CwHJ0x9NrikvqiaaWizNLsolGYvOcSmU5k/tYm0fJ5jqj8 6hBFsGN/BBfVXngRN9SRUP9YV9SoP0y0qliLVM4zg== X-ME-Sender: Received: from intern.anarazel.de (unknown [172.58.40.133]) by mail.messagingengine.com (Postfix) with ESMTPA id 9F4C37E13B; Mon, 27 Nov 2017 18:57:37 -0500 (EST) Date: Mon, 27 Nov 2017 15:57:24 -0800 From: Andres Freund To: Scott Marlowe Cc: Don Seiler , pgsql-performance@lists.postgresql.org Subject: Re: Setting effective_io_concurrency in VM? Message-ID: <20171127235724.ec2ludkit57gdkoy@alap3.anarazel.de> 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: Precedence: bulk Hi, On 2017-11-27 11:40:19 -0700, Scott Marlowe wrote: > tl;dr: Only way to know is to benchmark it. I'd guess that somewhere > between 10 and 20 is going to get the best throughput but that's just > a guess. Benchmark it and let us know! FWIW, for SSDs my previous experiments suggest that the sweet spot is more likely to be an order of magnitude or two bigger. Depends a bit on your workload (including size of scans and concurrency) obviously. Greetings, Andres Freund