4 ms·
Some will continue to prefer a self-hosted GitLab instance over GitHub, but requiring at least 4GB of RAM [1] for a low traffic instance sounds like an aberrati
by dessant 7y ago
Some will continue to prefer a self-hosted GitLab instance over GitHub, but requiring at least 4GB of RAM [1] for a low traffic instance sounds like an aberration. There should be better ways to manage memory consumption, and a lean GitLab instance that we have full control over could still be their selling point over GitHub.
[1] https://docs.gitlab.com/ce/install/requirements.html#memory https://docs.gitlab.com/ce/install/requirements.html#memory
- true_religion 7y agoGiving away your core product for free is hardly a “selling” point. As open source is all about scratching your own itch, their itch isn’t lean software because that isn’t what they run in their company.
- sytse 7y agoWe agree 4GB is too much. We put a team together to get the memory usage down https://about.gitlab.com/handbook/engineering/development/enablement/memory/ https://about.gitlab.com/handbook/engineering/development/en... They’re rolling Puma out as an application server on .com within weeks. After that is successful we’ll make that the default. That should save a lot. After that the memory team will keep improving it.
- bashy 7y agoI agree and my small instance run within Docker uses 2.5GB. I am glad I run mine on a system with 32GB RAM.
- craigg 7y agoHi this is Craig, the Engineering Manager for the Memory team. We're actively working on reducing the memory issues with GitLab. We are approaching this by responding to known issues and building out proactive tooling to inform developers of memory usage during the development cycle. You can follow along with our efforts on this board: https://gitlab.com/groups/gitlab-org/-/boards/1143987?label_name[]=Memory&label_name[]=group%3A%3Amemory https://gitlab.com/groups/gitlab-org/-/boards/1143987?label_...
- riffic 7y agomaybe you want another product? I hear Gitea is nice and lightweight.