From eb70beb1a57505128ac7e83122850e05f7b46aa7 Mon Sep 17 00:00:00 2001 From: Pablo Vizcay Date: Sun, 1 Oct 2017 12:14:57 -0300 Subject: [PATCH] add Puma internal threads explaining (#1425) * add Puma internal threads explaining * fixed typo --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 47141850..e8f881d2 100644 --- a/README.md +++ b/README.md @@ -74,6 +74,8 @@ $ puma -t 8:32 Puma will automatically scale the number of threads, from the minimum until it caps out at the maximum, based on how much traffic is present. The current default is `0:16`. Feel free to experiment, but be careful not to set the number of maximum threads to a large number, as you may exhaust resources on the system (or hit resource limits). +Be aware that additionally Puma creates threads on its own for internal purposes (e.g. handling slow clients). So even if you specify -t 1:1, expect around 7 threads created in your application. + ### Clustered mode Puma also offers "clustered mode". Clustered mode `fork`s workers from a master process. Each child process still has its own thread pool. You can tune the number of workers with the `-w` (or `--workers`) flag: