May be i was not doing something right.
Here you go:
> On a DigitalOcean droplet of 512MB
I'm not sure it's realistic to expect great performance on a tiny droplet in a budget provider that over-provisions the heck out of these tiny instance sizes.
Spend more than $5/month and you may get better results.
GitLab has actually a pretty large overhead, and for a single user, it requires quite a bit of CPU/RAM. I assume that the requirement is not lineal though.
User load is what bumps up the RAM requirements. If the active user count is in the single digits and you're running into problems with RAM, either something is deeply misconfigured on your server, you have a ton of data, or the codebase is poor.
Memory is cheap. GitLab's resource usage doesn't increase much from the baseline as you go from 1 user to 100 users. You just can't run it on a potato.
GitLab (and every other Rails app) makes the assumption that it's better to eager load an entire codebase once at boot time rather than to load code on demand and throw it away during a request.
That trades off baseline memory usage for runtime performance, and it's a perfectly valid 'engineering reason' for why GitLab's baseline memory usage is so high.
For less than the price of your $5 droplet, you get 4x the RAM and probably an equal amount of CPU.
Just don't expect much support from OVH because they're busy all the damn time.
The self hosted option may not be right for you especially if you're already using BitBucket private repos. Why did you not try GitLab's hosted private repos?