[PATCH] doc: document Etc.nprocessors for worker_processes

[PATCH] doc: document Etc.nprocessors for worker_processes

[Eric Wong]

Ruby 2.2 has Etc.nprocessors, and using that (directly or as a
factor) for setting worker_processes is often (but not always)
appropriate.
---
 TUNING | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/TUNING b/TUNING
index 542ebdc..6a6d7db 100644
--- a/TUNING
+++ b/TUNING
@@ -17,9 +17,12 @@ See Unicorn::Configurator for details on the config file format.
   \Unicorn is NOT for serving slow clients, that is the job of nginx.
 
 * worker_processes should be *at* *least* the number of CPU cores on
-  a dedicated server.  If your application has occasionally slow
-  responses that are /not/ CPU-intensive, you may increase this to
-  workaround those inefficiencies.
+  a dedicated server (unless you do not have enough memory).
+  If your application has occasionally slow responses that are /not/
+  CPU-intensive, you may increase this to workaround those inefficiencies.
+
+* Under Ruby 2.2 or later, Etc.nprocessors may be used to determine
+  the number of CPU cores present.
 
 * worker_processes may be increased for Unicorn::OobGC users to provide
   more consistent response times.
-- 
2.3.2.209.gd67f9d5