3 ms·
I ran a GitLab instance for a company pretty much solo and it never wound up going down outside of when I was upgrading it, that I can recall. The thing about t
by jchw 5y ago
I ran a GitLab instance for a company pretty much solo and it never wound up going down outside of when I was upgrading it, that I can recall. The thing about that is, it’s a small scale instance. If an upgrade or change failed, I could literally delete everything and restore from backup in under an hour, and never really needed to do that (although to be clear, I did actually test that it was possible.)
Now I’ll tell you the real problem with it: it worked great for people who were located in the U.S., but it was terrible for certain remote employees due to increased latency, and the fix for that would be to set up a complicated replication setup that puts data closer to people not near the main instance.
There’s obviously other issues, but that is one that is probably commonly overlooked that most SaaS solutions can do better on.
- Jarwain 5y agoWhat gitlab features do you utilize where latency actually is a problem? I currently manage an internal gitlab instance with some remote coworkers, but I haven't heard any complaints about latency. Although tbf, I feel like we've barely scratched the surface of what gitlab supports
- jchw 5y agoThe most impacted user had ~500ms latency to the server, which is enough that even pageloads are bound to feel slow (especially because Gitlab itself is not necessarily the fastest thing in the world sometimes.) And if I am remembering correctly, I think that was basically it: the UI pageloads just had enough chained round trips that they were way too slow. In retrospect, there may have been some ways to work around this that we didn’t end up exploring. When I moved to a new company, the GitLab instance was still up, and last I was aware, many years down the road, it is still in use. Feature-wise, we were very much satisfied, and the GitLab CI model with Docker executors worked very well for us.
- sytse 5y agoIf you have high latency to a GitLab server consider setting up a GitLab Geo server locally https://docs.gitlab.com/ee/administration/geo/ https://docs.gitlab.com/ee/administration/geo/ to improve things (this is a paid feature).
- jchw 5y agoLooks like you got downvoted for some reason, but yes, this is exactly what I am referring to. (We did pay for GitLab EE, so I think we had access to Geo.)