Fork Puma to validate scheduler fixes
What does this MR do?
Related to #36858 (closed)
This makes us to switch to use Puma from:
This is needed to test a latest latency improvements for Puma to improve, Puma scheduling mechanism described in detail in #36858 (closed).
This is meant to be temporary as part of effort to upstream the https://github.com/puma/puma/pull/2079, but first validate this patch on GitLab.com.
This forks the puma and puma_worker_killer.
All people mentioned in https://about.gitlab.com/handbook/developer-onboarding/#ruby-gems are additional owners of the above gems.
gitlab-puma
- Gem: https://rubygems.org/gems/gitlab-puma
- Pull request with tests: https://github.com/puma/puma/pull/2079
- Our changes: gitlab-puma@2986bc4a...gitlab-latency
gitlab-puma_worker_killer
- This is forked to make it depend on
gitlab-puma. - Our changes: https://gitlab.com/gitlab-org/gitlab-puma_worker_killer/compare/52d56d40ab2e22b48b23a8f55f01e77c34206a4a...gitlab-puma
Does this MR meet the acceptance criteria?
Conformity
Edited by Yorick Peterse