upvote

points

by margalabargala13 hours ago |
comments
upvoteby grogenaut12 hours ago|
next
[-]
I may have my timelines wrong but I don't remember github being rock solid 5 years ago. I remember multiple outages keeping us from pulling code for go packages that were not using an enterprise dependency cache and killing multiple days of work a year for those systems. It's what I used as a forcing function to move people TO an enterprise dependency cache, and to find the few scofflaws running work code off of github.com versus enterprise.
reply
upvoteby margalabargala11 hours ago|
parent|
[-]
You're right. I was misremembering this graph:

https://damrnelson.github.io/github-historical-uptime/

reply
upvoteby tlunch5 hours ago|
parent|
[-]
That is a pretty wild graph
reply
upvoteby someguyiguess6 minutes ago|
parent|
next
[-]
There is no way Github had 100% uptime prior to the MS acquisition. Nobody has 100% uptime 100% of the time. They must have changed how they were measuring uptime.
reply
upvoteby throwaway20374 hours ago|
parent|
prev|
next
[-]
Can you explain more of what you mean by "wild" here?

I never worked on any SaaS that had such high uptime. It seems pretty good to me. In 10 years, it was always better than 99.5% uptime. That seems impressive to me for a huge, complex SaaS like GitHub.

reply
upvoteby philipallstar4 hours ago|
parent|
[-]
I might be wrong, but isn't half a percent almost 2 days of downtime in a year?
reply
upvoteby someguyiguess5 minutes ago|
parent|
[-]
Or 7 minutes a day.
reply
upvoteby criley23 hours ago|
parent|
prev|
[-]
Feels like a pretty wildly misleading graph. What do they say about lies, damned lies and statistics?

This graph is literally designed to abuse correlation =/= causation by attaching the arbitrary label "microsoft acquires github" so that the reader will apply causation to the uptime.

Now let's overlay ontop of the uptime graph a few lines of: # of monthly active users, # of monthly commits, size of PRs, action minutes per PR (whatever demonstrates scaling)

Something tells me that the uptime issues follow scale more than they do ownership... but that's not the narrative that this chart was designed for...

reply
upvoteby aprentic2 hours ago|
parent|
[-]
The nice thing about statistics and math is that you don't need to stop at a feeling. If doubt their math, do it yourself.
reply
upvoteby slowmovintarget12 hours ago|
prev|
[-]
Security: No leaking PII, no compromised build pipelines.

Uptime: 4 9s minimum for paying customers for the core service (not necessarily the social features, but pull requests have to work).

reply
upvoteby pcdevils6 hours ago|
parent|
[-]
More AI it is
reply