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

Make puma default webserver #481

Merged
merged 3 commits into from
Oct 23, 2024
Merged

Make puma default webserver #481

merged 3 commits into from
Oct 23, 2024

Conversation

svkrieger
Copy link
Contributor

A short explanation of the proposed change:

Make Puma the default webserver as it has been running on big foundations and brings performance boosts, better resource utilization and is well maintained. Thin can be still enabled by using the newly introduced config parameter cc. temporary_enable_deprecated_thin_webserver . jemalloc is now enabled globally for all CAPI jobs providing better memory management.

  • Config cc.experimental.use_puma_webserver has been removed
  • Config cc.experimental.use_jemalloc_memory_allocator has been removed
  • Puma default config is 2 workers with each 10 threads and 10 DB connections
  • I have viewed signed and have submitted the Contributor License Agreement

  • I have made this pull request to the develop branch

  • I have run CF Acceptance Tests on bosh lite

Thin can still be used using the new config flag `cc.temporary_enable_deprecated_thin_webserver`
jochenehret
jochenehret previously approved these changes Oct 23, 2024
@svkrieger svkrieger merged commit 781690e into develop Oct 23, 2024
2 checks passed
@svkrieger svkrieger deleted the make-puma-default-webserver branch October 23, 2024 09:09
Samze added a commit that referenced this pull request Oct 24, 2024
@svkrieger svkrieger restored the make-puma-default-webserver branch October 25, 2024 12:41
svkrieger pushed a commit that referenced this pull request Oct 25, 2024
@svkrieger svkrieger mentioned this pull request Oct 29, 2024
3 tasks
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.

2 participants