What can also help is running the Omnibus package that restarts processes that start using too much memory automatically.
The Ruby on rails solution to memory leaks probably shouldn't be the goto remedy.
Preventing memory leaks is better than restarting. Please participate in https://gitlab.com/gitlab-org/gitlab-ce/issues/3700 to help.
gitlab IS a ruby on rails app
Why wouldn't a ruby on rails solution be right for a ruby on rails app?
Re:Making GitLab faster
by prawnsalad on Friday February 26, 2016 @05:17AM
(#11180692)
If the ruby on rails solution to memory leaks is to restart, then it's far better to actually get it fixed to not leak memory in the first place.
Restarting is just ignoring the issue.
I've heard a lot of good things about gogs for for running self-hosted git repositories on low-spec servers.
I've ran Gogs on the RaspberryPi2 and it felt quite fast (didn't do any serious work on it though)
edit:
- fix typo
- ps: i'm also looking forward to have some extra time to setup Gitlab on the Pi2 as well (either Docker preferably or https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2...)
I then switched providers, which also came with more system resources, and GitLab was working without any issues right away. It could have been caused by an oversold node at the previous host, or the slightly higher system specs at the new host made the difference, but I've been running GitLab on that new server for a couple of months now without experiencing those slowdowns again.
If you've noticed a gradual slowdown to the point of pages getting stuck on loading indefinitely, then try to up the system specs a bit, as it could make quite the difference.