3 ms·
Would switching from GitLab to something like Gitea/Gogs cut down on those costs? The GitLab system requirements start at multiple gigabytes of RAM and CPU core
by lucb1e 7y ago
Would switching from GitLab to something like Gitea/Gogs cut down on those costs? The GitLab system requirements start at multiple gigabytes of RAM and CPU cores for almost idle installations whereas a small Gitea I'm running takes <100MB RAM and next to zero CPU. Most people I know that self-host (i.e. privately, not commercially) a git server with issue tracker don't run GitLab due to the resource hogging. But I don't know how it scales when you put more load on Gitea vs the same load on GitLab -- does anyone have experience with that?
- stonogo 7y agoIt says in the message it's storing and serving build artifacts that is driving costs. This means the expense is in disk and bandwidth, not CPU and RAM. Switching to Gogs would cut down on the resources which are not identified as the problem.
- tiew9Vii 7y agoThey probably could use some cheap blob storage like Backblaze B2 which is very cheap ($0.005 GB/month storage, $0.01 G download) for storing artifacts then put Cloudflare in-front of it. If artifacts are treated as immutable most of the traffic will be from the CDN and as they are immutable can have a far future cache-control.
- earenndil 7y agoThe cost is bandwidth, not ram/storage.