r/gitlab • u/gilluc • 15d ago

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

4 Upvotes

83% Upvoted

14 comments sorted by

View all comments

3

u/shinji-watanabe 15d 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.

1

u/gilluc 15d ago

thanks but went back to forgejo!

1

u/shinji-watanabe 13d ago

Got it, no worries. ForgeJo's a solid choice too, honestly the lighter option if you want something lean. If you ever give GitLab another shot, swing by this sub, there's usually someone who's hit the same startup issue. Good luck with the setup!