Live data from Hacker News

Degraded performance on GitLab.com

gitlab.com

21–30 of 46 posts

Re: Degraded performance on GitLab.com

#22
post #5

Even though my builds won't start as runners seem to be blocked, it's kinda fascinating to see those in-depth details about the service and how the Gitlab dudes try to find the root cause.

Right? This is EXACTLY what I want to see when there's a service disruption.

A live, in-depth view of who is doing what, any new leads on the issue, multiple teams chiming in with various diagnostic stats, honestly it's really awesome.

I know this can't be expected from most businesses, especially non-open sourced ones, but it's so refreshing to see this instead of the typical "We're working on a potential service disruption" that we normally get.

Re: Degraded performance on GitLab.com

#23
post #5

Even though my builds won't start as runners seem to be blocked, it's kinda fascinating to see those in-depth details about the service and how the Gitlab dudes try to find the root cause.

Right? This is EXACTLY what I want to see when there's a service disruption. A live, in-depth view of who is doing what, any new leads on the issue, multiple teams chiming in with various diagnostic stats, honestly it's really awesome. I know this can't be expected from most businesses, especially non-open sourced ones, but it's so refreshing to see this instead of the typical "We're working on a potential service di…

I think it's cool but I'd be totally self-aware and fearful or making the idiot post in the thread for HN to judge :p

Re: Degraded performance on GitLab.com

#25
post #6

I was trying out Gitlab pages for the first time, but gave up since it was so slow, moving my stuff to Github. Guess it's not always that slow...

I can say for sure, that Gitlab is not running that slow all the time. However, the services run noticeably slower when the US awakes (I'm located in Germany), which is in the afternoon and evening around here. I have no stats, but it feels like builds and the site run smoother in the morning.

In case you're actually curious, we do publish our grafana stats here: https://dashboards.gitlab.com

Re: Degraded performance on GitLab.com

#27
post #8

I know this is probably a controversial post but seeing how big and bloated Gitlab became after years of devops dragon-chasing, i switched to gittea. https://gitea.io/en-us/ I keep separate CI and a separate wiki, so i can upgrade them independently and not have the entire software development process grind to a halt whenever I need to patch.

Hi GitLab employee, just gonna echo what the other person said and say that it isn't controversial to say that! We know that we don't work for every situation, if all you need is a repo, then by design we can't compete with how lightweight something like Gitea is.

Re: Degraded performance on GitLab.com

#28
post #17
post #4

GitLab is best (imo) as a private instance; we haven't had any issues with it after using it for 3 years now

Have you also tried Gogs? https://gogs.io

Gogs isn't exactly the same product though. If all you need is a git repo then sure, but it's all the other features that make GitLab more difficult to maintain

Re: Degraded performance on GitLab.com

#29
post #26

Not sure if this is related but I've received a bunch of emails from Gitlab stating my account is locked for too many failed password attempts. Possible DDoS?

We haven't had any other reports of this, please submit a ticket here if you think there's an issue so we can track it: https://support.gitlab.com/hc/en-us/requests/new?ticket_form...

Re: Degraded performance on GitLab.com

#30
post #11

I recently started a new position at a company that is using Gitlab. In the last month I've seen a lot of degraded performance and service outages (especially in Gitlab CI). And then I see stuff like this that makes me scratch my head: https://about.gitlab.com/product/service-desk/ If anyone at Gitlab is reading this ... please, please slow down on chasing new markets + features and just make the stuff you already ha…

For a bit more about WHY we choose breadth over depth - We believe that the company plowing ahead of other contributors is more valuable in the long run. It encourages others to contribute to the polish while we validate a future direction. You can read more on our company strategy page - https://about.gitlab.com/company/strategy/#breadth-over-dept...

As open-source software we want everyone to contribute to the ongoing improvement of GitLab.

Post reply on HN