2 ms·
I have somewhat similar experience. I have 16GB of RAM, 12 CPU. You can reduce the number of unicorn workers in `config/gitlab.rb`.
by Jugurtha 6y ago
I have somewhat similar experience. I have 16GB of RAM, 12 CPU.
You can reduce the number of unicorn workers in `config/gitlab.rb`.
- lbotos 6y agowhat are you seeing in the logs? OOM-killer? Also, newer versions use Puma which lower RAM needs if you are seeing Unicorn OOM Killer
- Jugurtha 6y agoAh, my bad. I have `12.10.6 (833223f2a7f)`. Time to pull, as it really hogged my RAM. The pattern is that it will periodically consume much more resources. Thanks for the heads-up.
- ianbooker 6y agoThat was a theory I had: That Unicorn leaks and that Unicorn Killer is not killing any of the workers, since it does so all 160 requests and there are no request happening at the moment. Then I saw the new installation uses Puma ;)
- joshlambert 6y agoHi, GitLab product manager here. I'm sorry that we haven't provided a good experience. We try really hard to make sure GitLab deployments "just work", and clearly it does not for either of you. Both Puma and Unicorn should be killed after they exceed a certain size to avoid this situation from happening. It's possible either this is not working in some situations/configurations, or there is a leak elsewhere although this is the first time I have heard reports of this. What configuration is being changed from the defaults? Alternatively if you could open an issue with any additional detail we will try to figure out what is happening and fix it: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues