3 ms·

Hope they put a lot of it (money) in their server infrastructure and better management of incident handling on gitlab.com. Thinks can break or get slow (sure) b

Hope they put a lot of it (money) in their server infrastructure and better management of incident handling on gitlab.com. Thinks can break or get slow (sure) but their competitor (github) is in comparison rock solid. I cannot even count the 503 or git downtimes on gitlab.com I hope they look on a lot of worse case scenarios like e.g. an upgrade breaks things, DB issues etc. and look how big big cloud installations are doing this stuff (staged updates, roll backs etc.)

btasovac 8y ago
We are heavily focusing on performance improvements - both in the product (so that features run better)[1] and in our GitLab.com infrastructure team (so that GitLab.com runs more reliably)[2]. Thank you for sharing your thoughts candidly. [1] - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label_name%5B%5D=performance https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label... [2] - https://gitlab.com/gitlab-com/infrastructure/issues https://gitlab.com/gitlab-com/infrastructure/issues
- adtac 8y ago
  I'll just say that gitlab.com, in my experience, has been much faster than it used to be the past few weeks. Things now don't take forever, which is a good thing. It's still slower than Github, but the improvement (due to the GCP migration?) is quite visible. Keep moving forward :)
  - pritianka 8y ago
    Yay! Thanks for sharing the positive experience. We know .com performance is something we need to improve and as mentioned in the comment above, are working super hard to get there.
  - mercer 8y ago
    Seconded. I moved to Gitlab because of pricing issues, and initially it felt sluggish to the point where I considered moving back to Github or Bitbucket (although the latter felt slow too). This is no longer the case. Things still feel sluggish, but not egregiously so.
shdh 8y ago
https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 https://status.gitlab.com/pages/history/5b36dc6502d06804c083...

btasovac 8y ago

We are heavily focusing on performance improvements - both in the product (so that features run better)[1] and in our GitLab.com infrastructure team (so that GitLab.com runs more reliably)[2]. Thank you for sharing your thoughts candidly. [1] - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label_name%5B%5D=performance https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label... [2] - https://gitlab.com/gitlab-com/infrastructure/issues https://gitlab.com/gitlab-com/infrastructure/issues

adtac 8y ago
I'll just say that gitlab.com, in my experience, has been much faster than it used to be the past few weeks. Things now don't take forever, which is a good thing. It's still slower than Github, but the improvement (due to the GCP migration?) is quite visible. Keep moving forward :)
- pritianka 8y ago
  Yay! Thanks for sharing the positive experience. We know .com performance is something we need to improve and as mentioned in the comment above, are working super hard to get there.
- mercer 8y ago
  Seconded. I moved to Gitlab because of pricing issues, and initially it felt sluggish to the point where I considered moving back to Github or Bitbucket (although the latter felt slow too). This is no longer the case. Things still feel sluggish, but not egregiously so.

shdh 8y ago

https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 https://status.gitlab.com/pages/history/5b36dc6502d06804c083...