5 ms·

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 th

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.
- GrayShade 9y ago
  https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2/ https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2... 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".
- the_duke 9y ago
  I'm running a Gitlab instance for a smallish dev team of 10. 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.
  - sytse 9y ago
    I'm surprised to hear GitLab isn't running reliably with 8GB. Are you running the Omnibus installations? The open issues for CE https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues do include feature requests.
awj 9y ago
> I'm sure part of this is the fault of the language. "Fault" is a pretty loaded word here. Pretty sure my old TI-86 also would struggle to run GitLab...

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.

GrayShade 9y ago
https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2/ https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2... 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".
the_duke 9y ago
I'm running a Gitlab instance for a smallish dev team of 10. 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.
- sytse 9y ago
  I'm surprised to hear GitLab isn't running reliably with 8GB. Are you running the Omnibus installations? The open issues for CE https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues do include feature requests.

awj 9y ago

> I'm sure part of this is the fault of the language. "Fault" is a pretty loaded word here. Pretty sure my old TI-86 also would struggle to run GitLab...