News for hackers. Stuff that matters.
Re:GitHub to layoff 10% and closing all offices by grepfru_it on Thursday February 09, 2023 @01:49PM (#34729091)
I wonder why they are not talking about the elephant in the room, the AWS spend. Cut back on that and these layoffs probably aren't necessary. The problem is the sheer size of GitHub data and the unreliability of Azure. There is an entire datacenter that is unused because data locality severely limits performance.
Re:GitHub to layoff 10% and closing all offices by mardifoufs on Thursday February 09, 2023 @02:35PM (#34729975)
Are they using both AWS and Azure?
Re:GitHub to layoff 10% and closing all offices by grepfru_it on Thursday February 09, 2023 @07:24PM (#34733821)
Yes
Re:GitHub to layoff 10% and closing all offices by umeshunni on Thursday February 09, 2023 @02:57PM (#34730380)
Moving from AWS to Azure is an order of orders of magnitude harder than moving from Zoom to Teams.
Re:GitHub to layoff 10% and closing all offices by grepfru_it on Saturday February 11, 2023 @11:28AM (#34753728)
My complaint is that MSFT had 3 years to focus on this problem and the solution today is to let go of engineers rather than prioritize minimizing costs (i guess in a way they did). There were EC2 snapshots dating back to 2013 when I last checked. Bad management gonna be bad
Re:GitHub to layoff 10% and closing all offices by ghthrowaway on Friday February 10, 2023 @12:29AM (#34735982)
This comment makes no sense. The “sheer size” is mostly repository and relational data, all of which is hosted on owned hardware in colo datacenters. GH AWS spend is almost entirely for internal CI. Lots of people would love to migrate that to azure to save money but they claim not to have the spare compute capacity.
Re:GitHub to layoff 10% and closing all offices by bato on Friday February 10, 2023 @04:39AM (#34737540)
Pretty much all new features from acquisition news are on azure (packages, codespaces etc).

Which is why outages usually match Azure outages.

Re:GitHub to layoff 10% and closing all offices by grepfru_it on Saturday February 11, 2023 @11:24AM (#34753682)
Hello fellow hubber? We still deploy new services using AWS or our own internal datacenters. Projects, for instance, is still run on k8s, not AKS. AE development was complicated from the start due to azure capacity, so much so that a tiger team went back to building it from scratch without azure.

Our AWS spending is outrageous tbh