Degraded performance on GitLab.com

#1

Post by sexy_devil » Mon, Jul 01, 2019, 3:05 PM UTC

Degraded performance on GitLab.com
gitlab.com

Re: Degraded performance on GitLab.com

#2

Post by grafelic » Mon, Jul 01, 2019, 3:26 PM UTC

Indeed. Incredibly slow.

Status page: https://status.gitlab.com/

Issue: https://gitlab.com/gitlab-com/gl-infra/production/issues/928

Re: Degraded performance on GitLab.com

#3

Post by bachmeier » Mon, Jul 01, 2019, 3:49 PM UTC

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...

Re: Degraded performance on GitLab.com

#4

Post by umvi » Mon, Jul 01, 2019, 3:56 PM UTC

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

Re: Degraded performance on GitLab.com

#5

Post by Kovah » Mon, Jul 01, 2019, 4:00 PM UTC

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.

Re: Degraded performance on GitLab.com

#6

Post by Kovah » Mon, Jul 01, 2019, 4:02 PM UTC

bachmeier wrote: post #3

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.

Re: Degraded performance on GitLab.com

#7

Post by wolf550e » Mon, Jul 01, 2019, 4:18 PM UTC

Is the conclusion that redis doesn't handle caching items that reach 99MB size each? I guess I would cache them in blob storage, not in RAM. And make sure to zstd them.

Re: Degraded performance on GitLab.com

#8

Post by nimbius » Mon, Jul 01, 2019, 4:24 PM UTC

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.

Re: Degraded performance on GitLab.com

#9

Post by tapoxi » Mon, Jul 01, 2019, 4:30 PM UTC

nimbius wrote: 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.

I don't think that's controversial, I think it's different use cases. If I want a simple git repo I'll go gogs/gitea, but GitLab is an all-in-one tool for a software shop.

Re: Degraded performance on GitLab.com

#10

Post by mr__y » Mon, Jul 01, 2019, 4:33 PM UTC

umvi wrote: 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

exactly my experience. Assuming that a powerful enough server is available to do that. Our first attempt to run gitlab on some small cheap VPS (2 cores, 4 gigs of ram) was a total disaster.