Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Puma internal threads explaining #1425

merged 2 commits into from Oct 1, 2017


None yet
2 participants
Copy link

commented Sep 30, 2017

According to talk into #531. Outdated
@@ -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 it's 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.

This comment has been minimized.

Copy link

nateberkopec Sep 30, 2017


it's -> its


This comment has been minimized.

Copy link
Contributor Author

commented Oct 1, 2017

Fixed typo @nateberkopec.

@nateberkopec nateberkopec merged commit eb70beb into puma:master Oct 1, 2017

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
continuous-integration/travis-ci/pr The Travis CI build passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.