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

foreman performance tuning #336

Merged
merged 21 commits into from
Jun 8, 2021
Merged

foreman performance tuning #336

merged 21 commits into from
Jun 8, 2021

Conversation

jhoblitt
Copy link
Member

This is an attempt to keep foreman more responsive by increasing the number of puma workers but reducing the number of active threads per worker to keep the total number of puma threads at 16. A system/cgroup memory limit of 16GiB is also applied along with puppetserver tuning.

@jhoblitt jhoblitt force-pushed the IT-2978/foreman-tuning branch 7 times, most recently from 5f93c6c to e6fdec0 Compare June 7, 2021 19:38
foreman is eventually becoming unresponsive with a single worker.  The
sole worker maxes out a core and then foreman is slow to respond.
Suspect this is due to locking in the ruby interpretor.  Running
multiple workers allow multiple cores to be used.
@jhoblitt jhoblitt force-pushed the IT-2978/foreman-tuning branch 2 times, most recently from 233189d to 819b900 Compare June 8, 2021 16:44
@jhoblitt jhoblitt merged commit 4a1fc8f into master Jun 8, 2021
@jhoblitt jhoblitt deleted the IT-2978/foreman-tuning branch June 8, 2021 23:41
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.

None yet

1 participant