Comment by lkramer
5 hours ago
For a long time I self hosted Gitlab, and was always quite happy with it, but I recently moved my VPS and decided to give Forgejo a try, and I have to say it's refreshing. It's really fast and takes a fraction of the resources Gitlab does. I'm sure Gitlab have more features, but frankly, I wasn't using them. I still like Gitlab, we use it at work and it does a good job, but for my own needs I don't see myself switching back any time soon.
It's frustrating that the so-called enterprise solutions are monsters. In a former workplace we were using Gogs for a long time. It's so nice to work with software that doesn't require a ton of resources for a relatively simple task.
We are running GitLab Ultimate in three different environments. Like 2000 users each and each user pipeline runs crazy like hundreds amounts of jobs. GitLab is keeping up. But we are sized for the 40 RPS architecture
> But we are sized for the 40 RPS architecture
Just in case anyone else (like me) didn't get the reference:
> This page describes the GitLab reference architecture designed to target a peak load of 40 requests per second (RPS), the typical peak load of up to 2,000 users, both manual and automated, based on real data.
https://docs.gitlab.com/administration/reference_architectur...
We used to run Gitlab Premium for around 300 users running hundreds of jobs over some monorepos. Gitlab suggested a small architecture using Omnibus, and while it helped a bit, it didn't perform as well under load as we expected it to.
Eventually, there was no virtual scaling that could help. This, for me, is the biggest problem with Gitlab hosting: as soon as you hit a scale where a single machine with Omnibus doesn't cut it, the jump in complexity, cost, and engineering hours is significant.
1 reply →
My experience also.
I would never use Gitlab for my own needs, but at company level, it's impressive how well it behaves!