doc: update effective_io_concurrency for SSDs

SSDs are no longer exotic, so recommend a default in the hundreds for
them.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index a82bf065a06b7fba2957ba24888f2239281f0e8e..061697b54cb1b996c3897478f5bb1cc2c8745875 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1944,20 +1944,16 @@ include_dir 'conf.d'
         </para>
 
         <para>
-         A good starting point for this setting is the number of separate
+         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.
-        </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.
+         SSDs and other memory-based storage can often process many
+         concurrent requests, so the best value might be in the hundreds.
         </para>
 
         <para>