Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.80)
	(envelope-from
 <pgsql-docs-owner+M8494=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
	id 1aWYo5-0003te-OJ
	for pgsql-docs@arkaria.postgresql.org; Fri, 19 Feb 2016 00:20:25 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84)
	(envelope-from
 <pgsql-docs-owner+M8494=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
	id 1aWYo5-00069t-4u
	for pgsql-docs@arkaria.postgresql.org; Fri, 19 Feb 2016 00:20:25 +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)
	(envelope-from <bruce@momjian.us>)
	id 1aWYnj-0005hy-2A
	for pgsql-docs@postgresql.org; Fri, 19 Feb 2016 00:20:03 +0000
Received: from momjian.us ([72.94.173.45])
	by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
	(Exim 4.84)
	(envelope-from <bruce@momjian.us>)
	id 1aWYnf-0003co-EN
	for pgsql-docs@postgresql.org; Fri, 19 Feb 2016 00:20:02 +0000
Received: from bruce by momjian.us with local (Exim 4.72)
	(envelope-from <bruce@momjian.us>)
	id 1aWYnd-00075n-FZ
	for pgsql-docs@postgresql.org; Thu, 18 Feb 2016 19:19:57 -0500
Date: Thu, 18 Feb 2016 19:19:57 -0500
From: Bruce Momjian <bruce@momjian.us>
To: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: effective_io_concurrency and SSDs
Message-ID: <20160219001957.GA27161@momjian.us>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="9jxsPFA5p3P2qPhR"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-docs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-docs.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@postgresql.org>
List-Post: <mailto:pgsql-docs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-docs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
X-Mailing-List: pgsql-docs
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org


--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I have created the attached doc patch to update effective_io_concurrency
to more accurately cover SSDs.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +

--9jxsPFA5p3P2qPhR
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="ssd.diff"

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
new file mode 100644
index a09ceb2..feb3777
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
*************** include_dir 'conf.d'
*** 1876,1895 ****
          </para>
  
          <para>
!          A good starting point for this setting is the number of separate
           drives comprising a RAID 0 stripe or RAID 1 mirror being used for the
           database.  (For RAID 5 the parity drive should not be counted.)
           However, if the database is often busy with multiple queries issued in
           concurrent sessions, lower values may be sufficient to keep the disk
           array busy.  A value higher than needed to keep the disks busy will
           only result in extra CPU overhead.
!         </para>
! 
!         <para>
!          For more exotic systems, such as memory-based storage or a RAID array
!          that is limited by bus bandwidth, the correct value might be the
!          number of I/O paths available.  Some experimentation may be needed
!          to find the best value.
          </para>
  
          <para>
--- 1876,1891 ----
          </para>
  
          <para>
!          For magnetic drives, a good starting point for this setting is the
!          number of separate
           drives comprising a RAID 0 stripe or RAID 1 mirror being used for the
           database.  (For RAID 5 the parity drive should not be counted.)
           However, if the database is often busy with multiple queries issued in
           concurrent sessions, lower values may be sufficient to keep the disk
           array busy.  A value higher than needed to keep the disks busy will
           only result in extra CPU overhead.
!          SSDs and other memory-based storage can often process many
!          concurrent requests, so the best value might be in the hundreds.
          </para>
  
          <para>

--9jxsPFA5p3P2qPhR
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

--9jxsPFA5p3P2qPhR--