4 ms·
I had the same guess... migrating from aws to azure & hitting some bumps. Have to assume they won't be very forthcoming about it if that is the reason.
by donkeydoug 7y ago
I had the same guess... migrating from aws to azure & hitting some bumps. Have to assume they won't be very forthcoming about it if that is the reason.
- masklinn 7y ago> migrating from aws to azure & hitting some bumps Could be the IO? I remember colleagues working on getting stuff running on azure and they experienced horrible IO latency, as well as very low throughput for lots of small IO (aka unix-style software). Was a few years back so it might have improved since, but if those things are still non-optimal and github is built with a unix-style vision of tons of small IO access… This specific outage taught me that github apparently stores git repos on-disk which I was not expecting though (because the API access complained it could not delete repos until they'd fully backed to disk or something).
- akx 7y agoI don't think they mainly run on AWS, but on "bare metal": https://github.com/holman/ama/issues/553 https://github.com/holman/ama/issues/553