diff options
| author | Bruce Momjian <bruce@momjian.us> | 2016-06-28 16:09:04 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2016-06-28 16:09:15 -0400 |
| commit | 46eafc8855d7c21e2c1a45faa77a3d5a2fc2c8b2 (patch) | |
| tree | dff2abc13ea647731eb7767010b3a5fe71ecd975 | |
| parent | b78364df1850a09ece442a138118f4be1a451366 (diff) | |
| download | postgresql-46eafc8855d7c21e2c1a45faa77a3d5a2fc2c8b2.tar.gz postgresql-46eafc8855d7c21e2c1a45faa77a3d5a2fc2c8b2.zip | |
doc: update effective_io_concurrency for SSDs
SSDs are no longer exotic, so recommend a default in the hundreds for
them.
| -rw-r--r-- | doc/src/sgml/config.sgml | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index a82bf065a06..061697b54cb 100644 --- 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> |