Skip to content

Add PerWorkerMaxMemoryMb to env variable for gitlab rails

Nikola Milojevic requested to merge add-per-worker-max-memory-mb-to-env into master

What does this MR do?

In Omnibus we are using Renderer to configure puma_per_worker_max_memory_mb. In CNG We use PUMA_WORKER_MAX_MEMORY env variable instead. This MR is setting PUMA_WORKER_MAX_MEMORY env variable if puma[per_worker_max_memory_mb] is configured.

We want to use PUMA_WORKER_MAX_MEMORY env variable in order to use this value outside of puma.rb and also to be consistent with CNG and k8s gitlab-com configuration.

Related issues

#7284 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened
Edited by Nikola Milojevic

Merge request reports