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

increase pm.max_children #1206

Merged
merged 1 commit into from
Nov 6, 2024
Merged

increase pm.max_children #1206

merged 1 commit into from
Nov 6, 2024

Conversation

TheVillageGuy
Copy link
Contributor

60 is too low, 70 runs a lot smoother

60 is too low, 70 runs a lot smoother
@melroy89 melroy89 merged commit a96ec89 into main Nov 6, 2024
7 checks passed
@melroy89 melroy89 deleted the increase-pm.max_children branch November 6, 2024 09:35
@melroy89
Copy link
Member

melroy89 commented Nov 6, 2024

Thank you for your contribution!

@BentiGorlich
Copy link
Member

I think the docs should state that this is a server specific config, depending on the size of your userbase and how active they are... It is like the postgresql tuning stuff just not one size fits all...

@melroy89
Copy link
Member

melroy89 commented Nov 6, 2024

Yes agreed, but for now I also agreed with increasing the max_children.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants