diff options
author | Eric Wong <e@80x24.org> | 2015-03-12 22:25:53 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2015-03-12 22:31:34 +0000 |
commit | 7d10e85c045a80df260dee1a6717483c5037ef56 (patch) | |
tree | 18e5569131d4e5482d479853c7e2844104d28d55 | |
parent | 20d0dee2cc93611256d5e6d11059a0c0cd23178c (diff) | |
download | unicorn-7d10e85c045a80df260dee1a6717483c5037ef56.tar.gz |
Ruby 2.2 has Etc.nprocessors, and using that (directly or as a factor) for setting worker_processes is often (but not always) appropriate.
-rw-r--r-- | TUNING | 9 |
1 files changed, 6 insertions, 3 deletions
@@ -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. |