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.

Sign up for GitHub

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

Fixes #38085 - Cap the number of Puma workers at 100 #1197

Merged
merged 1 commit into from
Dec 13, 2024
Merged

Fixes #38085 - Cap the number of Puma workers at 100 #1197

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions manifests/config.pp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,12 +86,14 @@
content => epp('foreman/database.yml.epp', $db_context),
}

# Capped at 100 because worst case that's 100 * (5 + 4) = 900 PostgreSQL connections for Katello or 100 * 5 = 500 for vanilla Foreman
ehelms marked this conversation as resolved.
Show resolved Hide resolved
# CPU based calculation is based on https://github.com/puma/puma/blob/master/docs/deployment.md#mri
# Memory based calculation is based on https://docs.gitlab.com/ee/install/requirements.html#puma-settings
$puma_workers = pick(
$foreman::foreman_service_puma_workers,
floor(
min(
100,
$facts['processors']['count'] * 1.5,
($facts['memory']['system']['total_bytes']/(1024 * 1024 * 1024)) - 1.5
)
Expand Down
Loading