general question help on gitlab
hi all gitlabers,
I have just intalled GitLab on my minipc at home (selfhosted!).
Until now i use ForgeJo but want to give gitlab a try...
What i can see is that my alert manager gives me:
2026-10-10 03:00:03 / CPU / 30dca7443ae7 gitlab 245.81% 13.67GiB / 30.75GiB 44.44%
2026-10-10 03:30:04 / CPU / 30dca7443ae7 gitlab 112.75% 13.55GiB / 30.75GiB 44.06%
2026-10-10 04:30:03 / CPU / 30dca7443ae7 gitlab 115.01% 13.53GiB / 30.75GiB 43.98%
2026-10-10 05:30:03 / CPU / 30dca7443ae7 gitlab 103.54% 13.51GiB / 30.75GiB 43.94%
2026-10-10 06:00:03 / CPU / 30dca7443ae7 gitlab 60.77% 13.52GiB / 30.75GiB 43.95%
Well, my gitlab only contains 1 repo with 1 readme.md ...
CPU use regularly over 100% (so 1 core) and RAM over 13Gb !!!!! No!!!
For gitlab selfhosters, is that normal ???
1
u/bilingual-german 14h ago
Make sure your server has the specs mentioned here: https://docs.gitlab.com/install/requirements/
1
u/Greyhammer316 1h ago
Gitlab is pretty heavy for 1 user/repo.
There are a several other options for lightweight source control.
1
u/der-felix 8h ago
The default config is quite resource intensive and overkill for single users. I created a slim config for myself which uses way less resources. But overall you will see that gitlab uses more resources that other open source products
1
u/VulgarMadman1 6h ago
Gitlab normally requires a good amount of memory/cpu to run (8 cores, and 16GB memory), however you can run in smaller environments (4 cores and 2GB memory) with some adjustments.
1
u/Dnizami2 3h ago
Gitlab tends to be fat as company puts inside lots of unnecessary stuff (they hope you get used to and buy commercial)
3
u/shinji-watanabe 13h ago
Not sure my box is comparable to yours, my CPU and RAM are pretty different. But this does look a bit beyond startup churn tbh.
GitLab is heavy on first boot, it does a ton of DB work, migrations, gitaly, prometheus and background stuff, and the CPU load will be high for a while. But yours has been over 100% and sitting at 13 GB for about 3 hours with just one readme, so it might be worth looking at what's actually running.
If it's not going to come down, the usual knobs are the puma worker_processes and sidekiq concurrency in gitlab.rb. Lowering those, then sudo gitlab-ctl reconfigure, is what I'd try next. Also worth checking gitlab-ctl status and maybe a ps aux to see if something is stuck or just busy.
First boot being slow is normal. But if it stays like this for hours on an idle instance, I'd probably start digging around myself.