Persistent memory issues—how to reduce/remove extra features?

[sixfold_distract]

I am using GitLab and have been inching up the memory usage over the life of the installation. Prior Git applications (gogs, gitea) were much leaner and faster and never had memory issues, but since moving to GitLab, it’s been a big problem. I’m now at 5.5 GB, but my server only has 8 GB, and for my uses, GitLab is definitely overkill.

From this GitLab docs page, there are a bunch of options, but it seems like there is some translation layer in order to enable these via Cloudron. How can I enable these features in Cloudron’s GitLab?

Thank you in advance.

[jdaviescoates]

@sixfold_distract said in Persistent memory issues—how to reduce/remove extra features?:

Prior Git applications (gogs, gitea) were much leaner and faster and never had memory issues, but since moving to GitLab, it’s been a big problem. I’m now at 5.5 GB, but my server only has 8 GB, and for my uses, GitLab is definitely overkill.

This doesn't answer your question (sorry, I don't know the answer), but I can't help wonder why you moved to GitLab? I don't have a need for any of them myself, but with only 8 GB I think I would've stuck with gogs or gitea

[girish]

This is sort of expected. GitLab is an enterprise product where memory is not a real cost concern. Our GitLab at https://git.cloudron.io runs with 8GB RAM. The server is a 128GB dedi even. I would say for personal and smaller usage, try gitea. That GitLab docs page seems quite outdated. Even normal rails app don't run well with 2GB. GitLab has like 4 separate things going on - rails, go, ssh, nginx, I am forgetting more.

[sixfold_distract]

Thanks for the answers—so to be clear it’s not possible to reduce the features as their docs suggest? (Through some rb config)

To be honest the gitea instance was hacked, so that was not ideal, and I switched from gogs to gitea awhile ago and cannot exactly recall why.