|
|
|
|
|
|
by RichieAHB
1134 days ago
|
|
|
In my experience “large distributed systems” don’t tend to be idling for 20% of the time? I think often such systems have some dependencies 24h a day. Even if it’s much lower in a 20% window you risk leaving clients out in the cold in that window, similarly to the post you linked, no? |
|
|
If your company is in Europe, and your gitlab instance goes down for 4hrs every day between 2.30am and 6.30am -- does anyone care? 0 people working those hours means 0 hours of lost dev time.
If you have 5 minutes of availability lost at 9.30 every morning it's much worse (at least in GameDev, when everyone is pulling the latest generated binaries). 900 people unable to work for 5 minutes is 75 hours of lost dev time; quite a lot more than 0 hours, even if the actual availability of the system was significantly higher.
If your audience is yourself, and people aren't supposed to be working, availability of those services is not necessary.
Hell. the Google SRE workbook goes into exactly this, so I know I'm not crazy.