3 ms·

I agree. I couldn't stand the slowness of Gitlab's UI. I originally came to Gitlab because Bitbucket was lagging on several features that I wanted, and had a po

by Watabou 10y ago

I agree. I couldn't stand the slowness of Gitlab's UI. I originally came to Gitlab because Bitbucket was lagging on several features that I wanted, and had a poor UI. Gitlab's UI seemed more inviting as it was similar to Github. Mostly though, I chose Gitlab for the free private repositories. The Gitlab UI is /fine/, but the speed is what gets me. On github, even if I have thousands of commits, the UI is instantaneous. If I click on something, the load time is less than a second for me. So I switched to Github and paid for the private repositories. I absolutely didn't mind paying for this since Github is so fast for me and seems to be adding pretty cool new features (code review enhancements on PR, for example). I still have one of my repositories on GitLab and it's still slow when I do things like browse commits, view source files, etc. It's not just Gitlab though. Bitbucket is pretty slow for me as well, though not as slow as Gitlab. I would guess that Github's caching algorithms are much better than either of those two to really make pages seem snappy.

pawadu 10y ago
yeah, gitlab _is_ slow. Given that they are (unlike github) actually making money I don't understand why they wont just throw more servers at the problem (or put some devs on fixing their backend).
- YorickPeterse 10y ago
  > I don't understand why they wont just throw more servers at the problem There's only so much you can solve by throwing more hardware/money at the problem. We have reached a point where we are wasting too much of this, so adding more won't help much. > (or put some devs on fixing their backend) We have plenty of people working on the problem, and for quite a while now. We're also hiring more developers to help us out with this: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope=all&state=merged&utf8=%E2%9C%93&label_name%5B%5D=Performance https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope... https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/3904 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... https://gitlab.com/gitlab-org/gitlab-ce/issues/25421/ https://gitlab.com/gitlab-org/gitlab-ce/issues/25421/ There's also this old (and closed) issue which contains a lot of information: https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42

by Watabou 10y ago

pawadu 10y ago

yeah, gitlab _is_ slow. Given that they are (unlike github) actually making money I don't understand why they wont just throw more servers at the problem (or put some devs on fixing their backend).

YorickPeterse 10y ago
> I don't understand why they wont just throw more servers at the problem There's only so much you can solve by throwing more hardware/money at the problem. We have reached a point where we are wasting too much of this, so adding more won't help much. > (or put some devs on fixing their backend) We have plenty of people working on the problem, and for quite a while now. We're also hiring more developers to help us out with this: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope=all&state=merged&utf8=%E2%9C%93&label_name%5B%5D=Performance https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope... https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/3904 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... https://gitlab.com/gitlab-org/gitlab-ce/issues/25421/ https://gitlab.com/gitlab-org/gitlab-ce/issues/25421/ There's also this old (and closed) issue which contains a lot of information: https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42