With Puma performance now validated to be within expectations (#64705 (closed)) the next steps are to define what the specific recommendations will be got Puma going forward (omnibus-gitlab#3896 (closed)) and update all relevant documentation to reflect this as the general switch from Unicorn to Puma.
This issue is for updating the docs. E.g. Switching any references to Unicorn to Puma.
I would say that we should continue using the same amount of workers, but configure by default to use T4.
We could propose that for some low-memory environments we would propose to use Wn/2, T4. This should allow to see memory reduction, but have a good overall performance.
The next requirement is to update a number of available connections, as with T4 we can use 4x more connections to Redis, PostgreSQL (unlikely, likely it will be around 1.5x-2x).
Do we actually know how many connections from pool we used during our testing compared Unicorn?
I didn't test connection limits specifically, they would've been whatever the defaults are in gitlab-ce docker image. We can explore testing that as well if required.
GitLab is moving all development for both GitLab Community Edition
and Enterprise Edition into a single codebase. The current
gitlab-ce repository will become a read-only mirror, without any
proprietary code. All development is moved to the current
gitlab-ee repository, which we will rename to just gitlab in the
coming weeks. As part of this migration, issues will be moved to the
current gitlab-ee project.
If you have any questions about all of this, please ask them in our
dedicated FAQ issue.
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to
rename gitlab-ce to gitlab-foss to make the purpose of this FOSS
repository more clear
I created a merge requests for CE, and this got closed. What do I
need to do?
Everything in the ee/ directory is proprietary. Everything else is
free and open source software. If your merge request does not change
anything in the ee/ directory, the process of contributing changes
is the same as when using the gitlab-ce repository.
Will you accept merge requests on the gitlab-ce/gitlab-foss project
after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in
gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git
remotes to use this new URL. GitLab will take care of redirecting Git
operations so there is no hard deadline, but we recommend doing this
as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?