Configuring Puma settings
- Determine suitable Puma worker and thread settings. For details, see Puma settings.
- Convert custom Unicorn settings to the equivalent Puma settings (if applicable). For details, see Converting Unicorn settings to Puma.
- For multi-node deployments, configure the load balancer to use the readiness check.
Reconfigure GitLab so the above changes take effect.
sudo gitlab-ctl reconfigure
For more details, see the Puma documentation.
Converting Unicorn settings to Puma
If you are still running Unicorn and would like to switch to Puma, server configuration will not carry over automatically. The table below summarizes which Unicorn configuration keys correspond to those in Puma, and which ones have no corresponding counterpart.
Puma Worker Killer
By default, the Puma Worker Killer will restart a worker if it exceeds a memory limit. Additionally, rolling restarts of Puma workers are performed every 12 hours.
To change the memory limit setting:
puma['per_worker_max_memory_mb'] = 850
Unlike Unicorn, the
puma['worker_timeout'] setting does not set maximum request duration.
A timeout of 60 seconds
is used when Puma is enabled. This limit is not configurable.