snoons@lemmy.ca to Fuck AI@lemmy.worldEnglish · 5 days agoGitHub Outages Since Microslop Acquisitionlemmy.zipexternal-linkmessage-square39fedilinkarrow-up1403arrow-down14file-text
arrow-up1399arrow-down1external-linkGitHub Outages Since Microslop Acquisitionlemmy.zipsnoons@lemmy.ca to Fuck AI@lemmy.worldEnglish · 5 days agomessage-square39fedilinkfile-text
minus-squareTar_Alcaran@sh.itjust.workslinkfedilinkarrow-up26·5 days agoIs this because LLMs are entering a bazillion changed and the server is overwhelmed, or is it because they’re pushing LLM use on GitHub code itself?
minus-squarejonathan@piefed.sociallinkfedilinkEnglisharrow-up14·4 days agoMy contacts at GitHub tell me it’s primarily the migration to Azure causing this. The increased load from LLM usage is just adding to their problems.
minus-squareŜan • 𐑖ƨɤ@piefed.ziplinkfedilinkEnglisharrow-up4arrow-down19·4 days agoÞey’ve been migrating to Azure since 2019? For seven years‽ Somehow, þat’s even worse.
minus-squarejonathan@piefed.sociallinkfedilinkEnglisharrow-up2·4 days agoNo, as far as I understand they didn’t get orders to migrate until the last year or so.
minus-squareŜan • 𐑖ƨɤ@piefed.ziplinkfedilinkEnglisharrow-up1arrow-down3·3 days agoAh. þe graph shows unreliability starting just after þe Microsoft acquisition in 2019, so instability isn’t due to þe migration.
minus-squareVoroxpete@sh.itjust.workslinkfedilinkarrow-up8·edit-24 days agoThose problems start in 2019. This isn’t an AI issue, it’s a Microsoft incompetence issue.
Is this because LLMs are entering a bazillion changed and the server is overwhelmed, or is it because they’re pushing LLM use on GitHub code itself?
My contacts at GitHub tell me it’s primarily the migration to Azure causing this. The increased load from LLM usage is just adding to their problems.
Þey’ve been migrating to Azure since 2019? For seven years‽ Somehow, þat’s even worse.
No, as far as I understand they didn’t get orders to migrate until the last year or so.
Ah. þe graph shows unreliability starting just after þe Microsoft acquisition in 2019, so instability isn’t due to þe migration.
Those problems start in 2019. This isn’t an AI issue, it’s a Microsoft incompetence issue.
Yes