undefined | Better HN

0 pointstossandthrow6d ago0 comments

I don't think commits per se puts pressure on the infrastructure.

More likely pulls and pushes, and, naturally, the ci minutes they identify as the main issue.

0 comments

But CI only increased by a factor of 2 since last year. Did they really not foresee that happening? And how does that affect git and api operations.

munk-a6d ago

It really shouldn't. The technical summary they released[1] is a very interesting read from a software engineering perspective. It seems to be blindsided by the increased traffic and gives stats related to commits/PRs (which should be relatively cheap for github to process) without any insight into their web traffic or details on how much actions are costing them. If they were super transparent they'd release information about their request response time and resourcing to fulfill that.

Their current path to resolution is to migrate their codebase to a new language[2], continue to drop their inhouse ops for Azure resources and get off MySQL. Maybe one or two of those steps are legitimately a good idea - I don't have an inside scope - but technology migrations are always fraught with issues. It's quite possible these changes are just a result of them vibe-coding a mature codebase into a new language.

1. https://github.blog/news-insights/company-news/an-update-on-...

2. I'll grant that Ruby isn't the best language to use as scale but I think we're all old enough to realize that language choice is far less impactful on performance than code quality.

hosh6d ago

Azure’s core hypervisor orchestrator was half-baked at launch and it was never been fixed. This long read blog series explains a lot for me — for example, why the FedRamp certification was never able to get a straight answer from Azure about how they handled secrets.

https://isolveproblems.substack.com/p/how-microsoft-vaporize...

spockz6d ago

Re 2, I would generally agree and there is a lot that can be done with caching. However, since writing services in Rust and Golang, there is whole other tier in speed. Architecture matters, code quality also matters, but Golang and Rust help a lot in making very fast services.

munk-a6d ago

Yeah I don't disagree. To clarify. Rust, Golang etc - they give you a very noticeable advantage when it comes to writing good performant software with the assumption that you're putting in the effort on the design side. But poorly written Rust is likely going to be indistinguishable from poorly written Ruby.

j / k navigate · click thread line to collapse

0 comments

NewJazz6d ago

But CI only increased by a factor of 2 since last year. Did they really not foresee that happening? And how does that affect git and api operations.

munk-a6d ago

1. https://github.blog/news-insights/company-news/an-update-on-...

2. I'll grant that Ruby isn't the best language to use as scale but I think we're all old enough to realize that language choice is far less impactful on performance than code quality.

hosh6d ago

https://isolveproblems.substack.com/p/how-microsoft-vaporize...

spockz6d ago

munk-a6d ago

j / k navigate · click thread line to collapse