mirror of
https://github.com/puma/puma.git
synced 2022-11-09 13:48:40 -05:00
add Puma internal threads explaining (#1425)
* add Puma internal threads explaining * fixed typo
This commit is contained in:
parent
6714214d57
commit
eb70beb1a5
1 changed files with 2 additions and 0 deletions
|
@ -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).
|
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
|
### 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:
|
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:
|
||||||
|
|
Loading…
Reference in a new issue