5 ms·

This is great news as Gitolite was the one thing that prevented me from giving Gitlab a try. What are the minimum requirements for a light Gitlab installation?

This is great news as Gitolite was the one thing that prevented me from giving Gitlab a try. What are the minimum requirements for a light Gitlab installation? I can't find any recommendations on the site. The thought of deploying Gitlab on a Linode 512 for $20 a month with virtually unlimited private repositories is very exciting.

sytse 14y ago
We don't have minimum requirements. We run GitLab.com with 3000+ users on a moderate (c1.medium, 1.7 GiB) instance. I think you will do fine with GitLab 5.0 and the 512 Linode. Might have to tune the default parameters a bit to have less processes running.
- randx 14y ago
  In order to run GitLab w/o any tweaks you need 1GB Linode. You can start it on 512 but you need to setup unicorn to use only 1 worker and you need at least 200MB of swap
  - nonpme 14y ago
    Is 1GB really requred for personal use? I thought about buying 256/512 VPS exclusively for GitLab, don't you think it will be enough for personal projects? Maybe someone who has the knowledge can write tutorial about configuring GL to run on average VPS?
    - sytse 14y ago
      A post about tuning GitLab for low memory consumption would be very useful indeed.
      - nonpme 14y ago
        Maybe someone will write one someday ;). And, as I have the chance, I want to thank you and whole GitLab team for a really great work! I'm using GL localy and I'm very pleased with it.
        sytse 14y ago
        Thanks nonpme, good to hear you are enjoying GitLab.
picomancer 14y ago
I'm running Gitlab 4.1 with more-or-less the default installation instructions and very light usage currently. I'll upgrade to 5.0 in the near future. Here's what I'm seeing: $ top PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1616 gitlab 20 0 1851m 108m 7112 S 0.0 10.9 7:46.35 ruby1.9.1 1405 gitlab 20 0 967m 99m 7044 S 0.0 10.0 0:26.63 ruby1.9.1 1667 gitlab 20 0 970m 98m 2596 S 0.0 9.9 0:01.36 ruby1.9.1 1670 gitlab 20 0 970m 97m 2488 S 0.0 9.9 0:00.77 ruby1.9.1 $ ps aux | grep [g]itlab USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND gitlab 1405 0.0 10.0 990904 101508 ? Sl Mar19 0:26 unicorn_rails master -c /home/gitlab/gitlab/config/unicorn.rb -E production gitlab 1616 0.1 10.9 1896392 110880 ? Sl Mar19 7:46 sidekiq 2.6.4 gitlab [0 of 25 busy] gitlab 1667 0.0 9.9 994156 100412 ? Sl Mar19 0:01 unicorn_rails worker[0] -c /home/gitlab/gitlab/config/unicorn.rb -E production gitlab 1670 0.0 9.9 994204 100284 ? Sl Mar19 0:00 unicorn_rails worker[1] -c /home/gitlab/gitlab/config/unicorn.rb -E production This doesn't include Redis or database. It seems like that's far too high. Why do you need 400MB of runtime data (and 5GB of allocation) in order to generate these relatively simple web pages? Ruby is bloated.

sytse 14y ago

We don't have minimum requirements. We run GitLab.com with 3000+ users on a moderate (c1.medium, 1.7 GiB) instance. I think you will do fine with GitLab 5.0 and the 512 Linode. Might have to tune the default parameters a bit to have less processes running.

randx 14y ago
In order to run GitLab w/o any tweaks you need 1GB Linode. You can start it on 512 but you need to setup unicorn to use only 1 worker and you need at least 200MB of swap
- nonpme 14y ago
  Is 1GB really requred for personal use? I thought about buying 256/512 VPS exclusively for GitLab, don't you think it will be enough for personal projects? Maybe someone who has the knowledge can write tutorial about configuring GL to run on average VPS?
  - sytse 14y ago
    A post about tuning GitLab for low memory consumption would be very useful indeed.
    - nonpme 14y ago
      Maybe someone will write one someday ;). And, as I have the chance, I want to thank you and whole GitLab team for a really great work! I'm using GL localy and I'm very pleased with it.
      - sytse 14y ago
        Thanks nonpme, good to hear you are enjoying GitLab.

picomancer 14y ago

I'm running Gitlab 4.1 with more-or-less the default installation instructions and very light usage currently. I'll upgrade to 5.0 in the near future. Here's what I'm seeing: $ top PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1616 gitlab 20 0 1851m 108m 7112 S 0.0 10.9 7:46.35 ruby1.9.1 1405 gitlab 20 0 967m 99m 7044 S 0.0 10.0 0:26.63 ruby1.9.1 1667 gitlab 20 0 970m 98m 2596 S 0.0 9.9 0:01.36 ruby1.9.1 1670 gitlab 20 0 970m 97m 2488 S 0.0 9.9 0:00.77 ruby1.9.1 $ ps aux | grep [g]itlab USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND gitlab 1405 0.0 10.0 990904 101508 ? Sl Mar19 0:26 unicorn_rails master -c /home/gitlab/gitlab/config/unicorn.rb -E production gitlab 1616 0.1 10.9 1896392 110880 ? Sl Mar19 7:46 sidekiq 2.6.4 gitlab [0 of 25 busy] gitlab 1667 0.0 9.9 994156 100412 ? Sl Mar19 0:01 unicorn_rails worker[0] -c /home/gitlab/gitlab/config/unicorn.rb -E production gitlab 1670 0.0 9.9 994204 100284 ? Sl Mar19 0:00 unicorn_rails worker[1] -c /home/gitlab/gitlab/config/unicorn.rb -E production This doesn't include Redis or database. It seems like that's far too high. Why do you need 400MB of runtime data (and 5GB of allocation) in order to generate these relatively simple web pages? Ruby is bloated.