9 ms·

If you're looking for the hosted version, there's lots of complaints about GitLab.com's performance. Bitbucket is quite excellent and integrates well with hoste

If you're looking for the hosted version, there's lots of complaints about GitLab.com's performance. Bitbucket is quite excellent and integrates well with hosted JIRA too - I'd say it's arguably a better option than GitHub in many cases. I've had good luck with self-hosted GitLab's performance in my small group, but I've heard tales of others who haven't, so try before you buy if you're doing that. The CI integration is really nice though and GitLab has put good work into that flow. It can also be the cheapest option and keeps you self-reliant if that's something that appeals to you.

dimitrieh 9y ago
Hi, GitLab UX Designer here. I would like to add that GitLab has put tremendous efforts in optimizing for performance lately. These performance optimisations optimise GitLab instances big and small. These improvements were triggered by having literally millions of users and projects on GitLab.com which is our hosted solution. For self-hosted GitLab instances run on a smaller scale, there should not even be a chance of performance hits :). Just to give a good overview of what GitLab is offering for both self-hosted as well as our hosted solution of GitLab.com please look at https://about.gitlab.com/features/ https://about.gitlab.com/features/ I am happy to hear that the CI/CD integration, which is our native solution for CI/CD and beyond is being well received! We want to persuade not force users to use our native solutions.
- clemmakesapps 9y ago
  GitLab frontend engineer here. Also wanted to add that performance improvement is a big part of our OKRs for our Q3 and are viewable at https://about.gitlab.com/okrs/ https://about.gitlab.com/okrs/
  - KallDrexx 9y ago
    I'm glad that it's such a priority that it's an OKR now, but there are public Gitlab issues talking about performance for the past 2 years. We did a full migration to Gitlab 3-6 months ago and had to migrate out into Bitbucket only a couple days later, as basic browsing operations proved to be way too consistently slow and was extremely aggravating. It will take a lot to prove to us that hosted Gitlab is actually good performance "for reals this time".
- jazoom 9y ago
  There's also the frequent downtime, often related to one NFS server, or something.
  - mydigitalself 9y ago
    We've been working quite a bit of our NFS storage topology and have recently introduced some remediation to prevent outages based on NFS availability. Previously an NFS failure would have pretty wide-reaching implications, now it's a lot more isolated. We're also working on an entirely new storage architecture for scaling and are slowly rolling this out. You can see more here: https://gitlab.com/gitlab-org/gitaly https://gitlab.com/gitlab-org/gitaly
    - jazoom 9y ago
      I knew you'd be working on something. I stick around because I love what you are building at GitLab.
ethomson 9y ago
If you're concerned about performance, Visual Studio Team Services hosts the world's largest Git repositories. (The largest being Windows itself.) And has to stay performant while doing it. Indeed, most people don't need to host repositories that large but we're proud that our performance scales out even to repositories that are massive. (ObDisclaimer: I work on VSTS.)

dimitrieh 9y ago

Hi, GitLab UX Designer here. I would like to add that GitLab has put tremendous efforts in optimizing for performance lately. These performance optimisations optimise GitLab instances big and small. These improvements were triggered by having literally millions of users and projects on GitLab.com which is our hosted solution. For self-hosted GitLab instances run on a smaller scale, there should not even be a chance of performance hits :). Just to give a good overview of what GitLab is offering for both self-hosted as well as our hosted solution of GitLab.com please look at https://about.gitlab.com/features/ https://about.gitlab.com/features/ I am happy to hear that the CI/CD integration, which is our native solution for CI/CD and beyond is being well received! We want to persuade not force users to use our native solutions.

clemmakesapps 9y ago
GitLab frontend engineer here. Also wanted to add that performance improvement is a big part of our OKRs for our Q3 and are viewable at https://about.gitlab.com/okrs/ https://about.gitlab.com/okrs/
- KallDrexx 9y ago
  I'm glad that it's such a priority that it's an OKR now, but there are public Gitlab issues talking about performance for the past 2 years. We did a full migration to Gitlab 3-6 months ago and had to migrate out into Bitbucket only a couple days later, as basic browsing operations proved to be way too consistently slow and was extremely aggravating. It will take a lot to prove to us that hosted Gitlab is actually good performance "for reals this time".
jazoom 9y ago
There's also the frequent downtime, often related to one NFS server, or something.
- mydigitalself 9y ago
  We've been working quite a bit of our NFS storage topology and have recently introduced some remediation to prevent outages based on NFS availability. Previously an NFS failure would have pretty wide-reaching implications, now it's a lot more isolated. We're also working on an entirely new storage architecture for scaling and are slowly rolling this out. You can see more here: https://gitlab.com/gitlab-org/gitaly https://gitlab.com/gitlab-org/gitaly
  - jazoom 9y ago
    I knew you'd be working on something. I stick around because I love what you are building at GitLab.

ethomson 9y ago

If you're concerned about performance, Visual Studio Team Services hosts the world's largest Git repositories. (The largest being Windows itself.) And has to stay performant while doing it. Indeed, most people don't need to host repositories that large but we're proud that our performance scales out even to repositories that are massive. (ObDisclaimer: I work on VSTS.)