4 ms·

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 complai

by 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.
  - the_duke 9y ago
    I'm using the official docker image. 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. ;)
    - sytse 9y ago
      Thanks for the answer. I would have thought that 4GB is enough. Thanks for providing a data point that it might not be.

by nisa 9y ago

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.
- the_duke 9y ago
  I'm using the official docker image. 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. ;)
  - sytse 9y ago
    Thanks for the answer. I would have thought that 4GB is enough. Thanks for providing a data point that it might not be.