5 ms·

for anyone new to gitlab, it is a bear. even their own cluster/HA documentation is mostly just a thin roadmap to a final goal. a statement of intent if you wi

for anyone new to gitlab, it is a bear. even their own cluster/HA documentation is mostly just a thin roadmap to a final goal. a statement of intent if you will. There are just far too many moving parts in this software and the glaring problem of "ruby doesnt scale well" is everpresent. packaged releases depend entirely on a bundled chef installation to get everything out the door and running. The software tries to do too much. CI/wiki/code review/git/container repository/analytics package. CI sharding per team and carving up gitlab into departments and groups has been my only solution so far, and its just distributed risk at that. its the difference between the unix ethos of do one thing and do it well, versus the F35 approach of do everything forever.

brianwawok 9y ago
On the flipside, I quite enjoy Gitlab. CI/CD that is very easy to use. I can self host it - so no $600 a month contract like some of the other guys. Decent Issues that are not as heavyweight as Jira. Place for code / CI/CD / Issues to all be in one place.
YorickPeterse 9y ago
> 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.
- GrayShade 9y ago
  I remember installing GitLab on a small NAS-type box. It was a while ago, but on each start-up it ran a nodejs tool to pre-compile some assets, I suppose. On that machine, it took 10-15 minutes to start. Afterwards, the unicorn workers kept getting killed because the default memory limit (128 MB) wasn't enough to process more than literally a couple of requests. It did work, but pages took 2-5 seconds to load, which I couldn't stand. For anyone needing a small Git Web UI, I suggest https://github.com/go-gitea/gitea 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.
  - brodock 9y ago
    IIRC this step is not needed/required anymore.
  - YorickPeterse 9y ago
    That sounds like the webpack development server was somehow started, which definitely is not required (or even recommended) for production setups.
  - kuschku 9y ago
    > For anyone needing a small Git Web UI, I suggest https://github.com/go-gitea/gitea https://github.com/go-gitea/gitea. 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).
    - GrayShade 9y ago
      Thanks for the heads-up. In my case I'm the single user, so it doesn't matter, but I'm sure it could handle a lot more. 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.
  - nisa 9y ago
    So just use cgit on your 128mb box and don't complain about gitlab? It's like installing Windows 10 on a machine with 1gb memory, starting Photoshop and complaining about swapping and that it's running slow. 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.
stephenr 9y ago
I find the GitLab approach a non-starter for me too. Both the "everything all in one" approach, and their insistence on "omnibus" packages that bundle fucking everything into a giant deb/rpm. Its unfortunate to me that there isn't a simple (as in cgit/gitweb/hgweb) oss repo web viewer that handles multiple repo types. I want issues, ci, project management separate.

brianwawok 9y ago

On the flipside, I quite enjoy Gitlab. CI/CD that is very easy to use. I can self host it - so no $600 a month contract like some of the other guys. Decent Issues that are not as heavyweight as Jira. Place for code / CI/CD / Issues to all be in one place.

YorickPeterse 9y ago

> 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.

GrayShade 9y ago
I remember installing GitLab on a small NAS-type box. It was a while ago, but on each start-up it ran a nodejs tool to pre-compile some assets, I suppose. On that machine, it took 10-15 minutes to start. Afterwards, the unicorn workers kept getting killed because the default memory limit (128 MB) wasn't enough to process more than literally a couple of requests. It did work, but pages took 2-5 seconds to load, which I couldn't stand. For anyone needing a small Git Web UI, I suggest https://github.com/go-gitea/gitea 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.
- brodock 9y ago
  IIRC this step is not needed/required anymore.
- YorickPeterse 9y ago
  That sounds like the webpack development server was somehow started, which definitely is not required (or even recommended) for production setups.
- kuschku 9y ago
  > For anyone needing a small Git Web UI, I suggest https://github.com/go-gitea/gitea https://github.com/go-gitea/gitea. 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).
  - GrayShade 9y ago
    Thanks for the heads-up. In my case I'm the single user, so it doesn't matter, but I'm sure it could handle a lot more. 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.
- nisa 9y ago
  So just use cgit on your 128mb box and don't complain about gitlab? It's like installing Windows 10 on a machine with 1gb memory, starting Photoshop and complaining about swapping and that it's running slow. 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.

stephenr 9y ago

I find the GitLab approach a non-starter for me too. Both the "everything all in one" approach, and their insistence on "omnibus" packages that bundle fucking everything into a giant deb/rpm. Its unfortunate to me that there isn't a simple (as in cgit/gitweb/hgweb) oss repo web viewer that handles multiple repo types. I want issues, ci, project management separate.