2020-01-15 03:08:55 +00:00
# Switching to Puma
## Puma
2020-03-25 15:07:47 +00:00
As of GitLab 12.9, [Puma ](https://github.com/puma/puma ) has replaced [Unicorn ](https://yhbt.net/unicorn/ ).
2020-05-14 09:07:53 +00:00
as the default web server. Starting with 13.0, both all-in-one package based
installations as well as Helm chart based installations will run Puma instead of
Unicorn unless explicitly specified not to.
2020-01-15 03:08:55 +00:00
## Why switch to Puma?
Puma has a multi-thread architecture which uses less memory than a multi-process
application server like Unicorn.
Most Rails applications requests normally include a proportion of I/O wait time.
During I/O wait time MRI Ruby will release the GVL (Global VM Lock) to other threads.
Multi-threaded Puma can therefore still serve more requests than a single process.
2020-04-22 00:09:24 +00:00
## Configuring Puma to replace Unicorn
If you are currently running Unicorn and would like to switch to Puma, server configuration
will _not_ carry over automatically. For details on matching Unicorn configuration settings with
the Puma equivalent, where applicable, see [Converting Unicorn settings to Puma ](https://docs.gitlab.com/omnibus/settings/puma.html#converting-unicorn-settings-to-puma ).
2020-01-15 03:08:55 +00:00
## Performance caveat when using Puma with Rugged
For deployments where NFS is used to store Git repository, we allow GitLab to use
[Direct Git Access ](../gitaly/#direct-git-access-in-gitlab-rails ) to improve performance via usage of [Rugged ](https://github.com/libgit2/rugged ).
Rugged usage is automatically enabled if Direct Git Access is present, unless it
is disabled by [feature flags ](../../development/gitaly.md#legacy-rugged-code ).
MRI Ruby uses a GVL. This allows MRI Ruby to be multi-threaded, but running at
most on a single core. Since Rugged can use a thread for long periods of
time (due to intensive I/O operations of Git access), this can starve other threads
that might be processing requests. This is not a case for Unicorn or Puma running
in a single thread mode, as concurrently at most one request is being processed.
We are actively working on removing Rugged usage. Even though performance without Rugged
is acceptable today, in some cases it might be still beneficial to run with it.
Given the caveat of running Rugged with multi-threaded Puma, and acceptable
performance of Gitaly, we are disabling Rugged usage if Puma multi-threaded is
used (when Puma is configured to run with more than one thread).
This default behavior may not be the optimal configuration in some situations. If Rugged
plays an important role in your deployment, we suggest you benchmark to find the
optimal configuration:
- The safest option is to start with single-threaded Puma. When working with
Rugged, single-threaded Puma does work the same as Unicorn.
- To force Rugged auto detect with multi-threaded Puma, you can use [feature
flags](../../development/gitaly.md#legacy-rugged-code).
