4 ms·
Fixed cost per IOPS allocated. Essentially, the same thing as before, but without the necessity of you storing large blank objects.
by freeone3000 6y ago
Fixed cost per IOPS allocated. Essentially, the same thing as before, but without the necessity of you storing large blank objects.
- vlovich123 6y agoHow 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?
- freeone3000 6y ago1) 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.
- fuzzyengineer 6y agoCan't this be addressed by provisioned throughput on EFS?
- deleted 6y ago[deleted]