-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Optimizing the pm.max_children setting #75
Comments
I didn't find any way to configure it with docker-compose.yaml You can configure it using Dockerfile
|
First you must determine if you really need to update this value. When you see this warning, this means that the current pool cannot serve every request in realtime and requests are put in a queue. It is perfectly ok if you see this once in a while. It is not realistic to think that any server always has slots waiting to serve new requests. A lot of the time you are in a queue for a few ms. The real question is: do you experience slowdowns? Do you get complaints about the performance? Also remember that settings values too high can have the opposite effect. It depends on your machine and use-case. |
I'm getting this warning on a vanilla Leantime docker installation:
How do I update this setting within docker compose?
Related issue: Leantime/leantime#2355
The text was updated successfully, but these errors were encountered: