GitHub degraded performance – resolved • Hacker News Board

Re: GitHub degraded performance – resolved

#11

Post by onionisafruit » Thu, Oct 21, 2021, 4:00 PM UTC

dabeeeenster wrote: post #9

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

How does moving to the Enterprise plan help?

Presumably GP means they will deploy their on GitHub Enterprise server instead of using github.com.

Re: GitHub degraded performance – resolved

#12

Post by rightbyte » Thu, Oct 21, 2021, 4:07 PM UTC

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

> I do agree that it's ridiculous to assume that we can manage Github's software better than their own engineers

Not really. You can mess with stuff when it suits you with a risk for downtime. Hosting yourself has the same advantage as disabling auto-updates - you are in control of when to break stuff.

Re: GitHub degraded performance – resolved

#13

Post by roland35 » Thu, Oct 21, 2021, 4:08 PM UTC

funOtter wrote: post #3

I was just doing some development on my GitHub Actions ... can only assume it was my fault.

Should have probably left out that sudo rm -rf from your Action

Re: GitHub degraded performance – resolved

#14

Post by andrewstuart2 » Thu, Oct 21, 2021, 4:12 PM UTC

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

I think you will quickly find if you're just deploying GH Enterprise on premises that it is not at all what you get from the GH Cloud offering. GHE has its own product roadmap that is quite a bit behind the cloud product, and in many cases (IMO) unacceptably so. It still doesn't support cache for runners, last I checked, though I've since moved on from the org that required me to work with GHE. I'm back to my happy place with self-hosted GitLab, and a little bit of GitHub cloud.

Re: GitHub degraded performance – resolved

#15

Post by awestroke » Thu, Oct 21, 2021, 4:20 PM UTC

mabbo wrote: post #4

In the middle of onboarding with a new company. We're at a critical point of training that requires GitHub. Oh boy, this is going to be a fun day.

The incident lasted less than an hour. How does this affect your whole day?

Re: GitHub degraded performance – resolved

#16

Post by mot2ba » Thu, Oct 21, 2021, 4:27 PM UTC

This incident has been marked as resolved. You guys could check how often Github notable incidents that really captures the audience's attention in HN [0] [1]:

[0]https://news.ycombinator.com/from?site=githubstatus.com

[1]https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=fal...

Re: GitHub degraded performance – resolved

#17

Post by cmckn » Thu, Oct 21, 2021, 4:30 PM UTC

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

> It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process.

I know outages are frustrating, but how does 30 minutes before 10am ruin an entire day? Maybe you’re just being hyperbolic, but people take coffee breaks longer than that.

Re: GitHub degraded performance – resolved

#18

Post by bob1029 » Thu, Oct 21, 2021, 4:38 PM UTC

andrewstuart2 wrote: post #14

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

I think you will quickly find if you're just deploying GH Enterprise on premises that it is not at all what you get from the GH Cloud offering. GHE has its own product roadmap that is quite a bit behind the cloud product, and in many cases (IMO) unacceptably so. It still doesn't support cache for runners, last I checked, though I've since moved on from the org that required me to work with GHE. I'm back to my happy p…

> GHE has its own product roadmap that is quite a bit behind the cloud product

This is exactly what we want though. We don't need the new fancy shit on a regular cadence. Issues, Code, PRs and 1 line checkbuild scripts are all we care about. Everything else is built into our software.

Re: GitHub degraded performance – resolved

#19

Post by lima » Thu, Oct 21, 2021, 4:40 PM UTC

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

> I do agree that it's ridiculous to assume that we can manage Github's software better than their own engineers

Why? It's totally reasonable that your own GHE instance will have better uptime.

Running GitHub.com is much, much harder than a private instance (DB scale-out, load, ...).

Our in-house Gerrit infra and CI has had a significantly better uptime than GitHub over the past year, but we have hundreds, not 60 million users and exabytes of storage :-)

Re: GitHub degraded performance – resolved

#20

Post by nonbirithm » Thu, Oct 21, 2021, 4:43 PM UTC

bob1029 wrote: post #6

This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process. When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically y…

> It's basically a lost day of productivity even if GH goes down for only 30 minutes.

Are we entering an era where if we don't have hundreds of thousands of servers running 24/7 to host our services, with all the resource consumption and environmental implications that result, that we will no longer be able to remain productive as a society? Is this gradually becoming a new baseline for humanity from which we cannot reasonably downsize?