5 ms·
I was running a self hosted gitlab instance on my homelab, but got annoyed with rails (and especially sidekiqs) runaway memory usage. In my own rails projects
by manchmalscott 4y ago
I was running a self hosted gitlab instance on my homelab, but got annoyed with rails (and especially sidekiqs) runaway memory usage.
In my own rails projects I’ve helped mediate this by compiling ruby from source with jemalloc, but honestly I don’t have the mental bandwidth to hack into their whole omnibus thing, so I just switched over to gitea instead.
- corrral 4y agoWhen I was evaluating options for a self-hosted web git service, I ruled out GitLab because I regard such high resource use as a serious architecture smell. Just asking for trouble. Also went with gitea. Runs on a potato. If you have few enough users you can stick with SQLite to make it stupid-easy to deploy and administrate.
- bityard 4y agoTo be fair, gitlab is designed for enterprise-scale deployments not a homelab or even a small team. It's like deploying an openstack cluster when you just need a few VMs. I'm on the tools team of a mid-size company and gitlab works very well for our 200ish developers. The only real pain point for us is the difficulty of upgrading combined with the high tempo release cadence.
- Spivak 4y agoOh hey, another jemalloc user! We just LD_PRELOAD it.