411–420 of 449 posts
Earlier quoted context omitted.
I don't think so. GitHub was bought by Microsoft 8 years ago and people have only started complaining about its uptime in the last year or so - exactly correlating with the surge in LLM use.
https://damrnelson.github.io/github-historical-uptime/ Seems pretty conclusive. Very similar story when they bought skype.
Earlier quoted context omitted.
reliable? Windows is the only operating system you have to constantly reinstall because it gets slower after a few months. To the point people think it's totally normal to do that!
Wait. That's not normal? My WSL instances end up getting overwritten when I reinstall Windows so I thought that was just a general OS thing...
Every bare-metal Linux system I have in my home is upgraded in-place. My oldest is roughly twenty years old. My newest is around four years old.
Earlier quoted context omitted.
> What is happening at GH? In large part, the move from AWS to Azure. Azure's just bad.
wasn't that years ago? or was that Skype? hahaha
Azure remains too bad to move Github to, but the relevant executives have pretty clearly decided that that's no longer a good reason to delay the move.
Earlier quoted context omitted.
> What is happening at GH? In large part, the move from AWS to Azure. Azure's just bad.
Based on previous posts I've seen about this, IIRC the timing seems to imply that it has more to do with them being hammered with AI slop than it does with the Azure transition. Who really knows though
It can be both things. I've worked professionally with AWS, Azure, and GCP, and Azure is just really flaky and unreliable. It's easily the worst of the three.
Earlier quoted context omitted.
Yeah, I think this one might be the straw that broke the camel's back and our team will look to migrate to something non-microsoft to be away from this nonsense.
What are the alternatives?
Earlier quoted context omitted.
I've always thought it was unfair that the 9 in 9% uptime doesn't count.
"1 nine" tends to mean "90% availability" i.e. 37 days of downtime per year. 9% availability would be an uptime of ~33 days a year, I think at that point, we're pushing the semantics of "available" if the service is down the entire year except one month on average.
I don't think this portents anything great for software in general. We're a good year+ into the use LLMs for all major bits of software that we all rely upon and GitHub here is down to one 9 of uptime. I've been using GitHub for a _long_ time, my first commits there go back to August 2009!, and I honestly don't recall GitHub going down as much as it has in the last year. I'm sure there's other things happening in the…
Are these outages caused by introduced bugs, though, or by load issues? As someone who has spent many years working in high load environments, this is not an uncommon pattern. You design a system and it works great. It can handle failures, load spikes, it is horizontally scalable, things are great. You think you figured it out. And then load keeps increasing and you suddenly hit a tipping point where everything keeps…
I don't think this portents anything great for software in general. We're a good year+ into the use LLMs for all major bits of software that we all rely upon and GitHub here is down to one 9 of uptime. I've been using GitHub for a _long_ time, my first commits there go back to August 2009!, and I honestly don't recall GitHub going down as much as it has in the last year. I'm sure there's other things happening in the…
Are these outages caused by introduced bugs, though, or by load issues? As someone who has spent many years working in high load environments, this is not an uncommon pattern. You design a system and it works great. It can handle failures, load spikes, it is horizontally scalable, things are great. You think you figured it out. And then load keeps increasing and you suddenly hit a tipping point where everything keeps…
With GitHub, we threw that away. It's centralized on steroids. Now we're all depending on one platform that has to be massively scaled to deal with the massive load of serving almost every major software project on the planet. And when it is down, we all notice.
Earlier quoted context omitted.
Except anything I'd self host would be down much more often. I've hardly ever actually experienced down time issues with github when I needed it.
Then you would be exceptionally bad at selfhosting as Github has like one nine of uptime.
Earlier quoted context omitted.
Except anything I'd self host would be down much more often. I've hardly ever actually experienced down time issues with github when I needed it.
I've never understood this argument. Even if self-hosted things were offline more often (which I've never found to be the case, I've had Forgejo + runners running for a year now with no downtime), the real benefit is that you yourself can work to bring it back online when it does, rather than waiting on a large, slow-moving organization to figure out what slopped PR caused their global service serving ungodly amounts…