Post Mortem of Google Outage on 14 December 2020

Re:Post Mortem of Google Outage on 14 December 2020 by freeone3000 on Friday December 18, 2020 @07:15PM (#25473686)

Fixed cost per IOPS allocated. Essentially, the same thing as before, but without the necessity of you storing large blank objects.

[ Parent | on HN ]

Re:Post Mortem of Google Outage on 14 December 2020 by vlovich123 on Friday December 18, 2020 @07:44PM (#25473874)

How would scheduling of concurrent I/O workloads work? If I’m paying some price per 1k IOPs and my service gets a spike, won’t I greedily take out the other services running on the same machine rather than getting throttled? Doesn’t this also penalize workloads that do lots of small I/Os rather than a few big ones even if the amount transferred is the same?

[ Parent | on HN ]

Re:Post Mortem of Google Outage on 14 December 2020 by freeone3000 on Friday December 18, 2020 @08:07PM (#25474010)

1) By ensuring capacity for max allocated concurrent IOPS

2) Wrong relationship; you're paying for IOPS to the block store, so you'd be trampling on other accesses to the same block store.

3) This penalizes them less - in that workloads that do lots of small IO on small files will actually be able to request the IOPS they need, instead of IOPS being (wrongly) dynamically allocated.

[ Parent | on HN ]

Re:Post Mortem of Google Outage on 14 December 2020 by fuzzyengineer on Friday December 18, 2020 @08:25PM (#25474122)

Can't this be addressed by provisioned throughput on EFS?

[ Parent | on HN ]