Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An update on GitHub availability

github.blog

Post reply on HN
Print view View original

21–30 of 266 posts

Re: An update on GitHub availability

#21

Post by ncruces »

maccard wrote: post #15
darkwater wrote: post #7

Glad that they released some data about new repo/issues/commits over the last years. It confirms what everyone else already believed from the outside: agents are putting a lot of extra, sudden pressure on GitHub. It's like a startup that is growing exponentially, with the difference that they already have a large user base to serve - and that keeps them in the bullseye - and probably a not-so-fast-moving organization…

What data is that? There's an unlabelled graph and a number at the current peak.

Some previous numbers: https://x.com/kdaigle/status/2040164759836778878

Re: An update on GitHub availability

#22

Post by ramon156 »

maccard wrote: post #13

It's kind of hard to read this with a straight face. The unlabelled graph with big numbers on top, the priorities that don't match with what we're experiencing, and a list of things that they're doing without a real acknowledgement of the _dire_ uptime over the last 12 months....

"We hear you" in ~300 words, basically.

Re: An update on GitHub availability

#23

Post by jftuga »

Some interesting tid bits:

* we had to resolve a variety of bottlenecks that appeared faster than expected from moving webhooks to a different backend (out of MySQL)

* * redesigning user session cache to redoing authentication and authorization flows to substantially reduce database load.

* we accelerated parts of migrating performance or scale sensitive code out of Ruby monolith into Go.

I'd like to know what database backend they migrated to. I was also surprised to read that the migration from Ruby to a more performant language had not already been completed. I assume this is because it a large code base with many moving parts, etc.

Re: An update on GitHub availability

#25

Post by ramon156 »

icy wrote: post #18

I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.). Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).

Love the idea, would replace the LLM generated content ony our site, though.

I recently migrated to codeberg because I'm okay with self-hosting big runners, while using codeberg's available runners for smaller cron-based things (they even have lazy runners for this).

Re: An update on GitHub availability

#26

Post by ncruces »

maccard wrote: post #13

It's kind of hard to read this with a straight face. The unlabelled graph with big numbers on top, the priorities that don't match with what we're experiencing, and a list of things that they're doing without a real acknowledgement of the _dire_ uptime over the last 12 months....

More numbers: https://x.com/kdaigle/status/2040164759836778878

What's the question here, you don't believe growth is currently exponential, or do you think it shouldn't be hard to scale, when 10x YoY is not enough?

Re: An update on GitHub availability

#28

Post by ArcHound »

icy wrote: post #18

I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.). Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).

But, there are? I can host a repo on GitHub, Codeberg and self host it too. Then I need to watch over main to keep it consistent between those. After that's established, I can do updates from wherever. Link'em in the README.

Re: An update on GitHub availability

#29

Post by beernet »

icy wrote: post #18

I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.). Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).

What is "sovereign infra" exactly?

Re: An update on GitHub availability

#30

Post by jasoncartwright »

cyanydeez wrote: post #20
jasoncartwright wrote: post #9

Earlier quoted context omitted.

Seems pretty sensible to not rely on a single provider for their large complex system?

This isn't a mom and pop shop. They have locations all over the world: https://datacenters.microsoft.com/ There's no intrinsic reason they should be vulnerable to themselves.

That website (for me) uses Cloudflare via WPEngine, which also isn't Azure
Post reply on HN