3 ms·
I'm running a Gitlab instance for a smallish dev team of 10. I haven't gotten it to run reliably with any less than 8Gb, even though we don't have a whole lot
by the_duke 9y ago
I'm running a Gitlab instance for a smallish dev team of 10.
I haven't gotten it to run reliably with any less than 8Gb, even though we don't have a whole lot of activity there.
It takes surprisingly long to start up too, even on a relatively beefy host.
I do like the product though, the all-in-one solution with code hosting, issues, code review (needs work though...) and CI is great. (Not using the deployment, orchestration stuff).
My biggest issue is that they seem to be too focused on pumping out new features.
There are 9k open issues just for CE. That's probably 12k+ for all products (runner, EE,...).
That either is a sign of very bad project management or a way to big agenda. Probably both.
- sytse 9y agoI'm surprised to hear GitLab isn't running reliably with 8GB. Are you running the Omnibus installations? The open issues for CE https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues do include feature requests.
- the_duke 9y agoI'm using the official docker image. It's been very pain-less in setup and maintainance. Upgrades were mostly painless as well until now. With 8GB for the docker container it's solid and pretty stable, but any less and behaviour would be very unstable (timeouts, very long request load times, ...). Of course those 8GB are for the whole stack (Postgres, Redis, Nginx, Unicorn instances, ...), so I'll admit that 8GB for the Docker container is quite important context here. ;)
- sytse 9y agoThanks for the answer. I would have thought that 4GB is enough. Thanks for providing a data point that it might not be.