> and the glaring problem of "ruby doesnt scale well" is everpresent
GitLab has many performance problems (and many have been solved over the years), but Ruby has thus far not been one of them. > and the glaring problem of "ruby doesnt scale well" is everpresent
GitLab has many performance problems (and many have been solved over the years), but Ruby has thus far not been one of them.For anyone needing a small Git Web UI, I suggest https://github.com/go-gitea/gitea.
EDIT: Oh, you're that guy ^^;.
Anyway, my rant was probably a bit harsh. I know that GitLab isn't really written for hardware comparable to a Raspberry Pi and that it's used by small and large teams all over the world. But on my hardware Gitea renders pages in 20-100 ms, which is orders of magnitude faster than GitLab. I'm sure part of this is the fault of the language.
But be aware, gitea (like gogs) does NOT cache SQL queries, so you are heavily limited by that. I can’t get it to serve > 200 pageloads per second on my system, while even a normal Grails projects manages to serve 3000 (with more complicated queries).
It used to cache something, either SQL queries or rendered pages, but it might have stopped in the meanwhile.
You made me curious, so I just tested it: 102 rps on a project page, 365 rps on a user profile, as reported by wrk2.
Gitlab runs fine out of the box with 4gb memory and when screwing with some provided knobs it's fine with 2gb or less memory.
It's in the docs, it's in every FAQ, every Stackoverflow answer... so why the hate?
64mb memory? Use gitolite. 256mb memory? Use cgit + gitolite 1gb memory? use gitea or whatever else there is. 4gb memory? use gitlab if you want.
I'm not affiliated but I can't stand the "gitlab doesn't run on my home wifi router - it sucks" posts here... it works pretty well if you read & acknowledge the documentation and requirements.
My box has 16 GB of memory. The 128 MB value was the default value configured in unicorn. If you're not familiar with that (I wasn't), it has a feature to restart the web server workers when they end up using too much memory. That's what unicorn does and apparently it's what people do in Ruby web apps.
I've also used GitLab on a (real) server. It still feels too slow for my taste (pages load in 1-2s). No, it's not unusable, but I won't call that "fine".
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.
The open issues for CE https://gitlab.com/gitlab-org/gitlab-ce/issues do include feature requests.
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. ;)
"Fault" is a pretty loaded word here. Pretty sure my old TI-86 also would struggle to run GitLab...