3 ms·
Note cloud vendors get the benefit of mixing high IOPs workloads with low IOPs workloads. Say a cloud vendor needs a bunch of HDD for a database workload with
by cobookman 7y ago
Note cloud vendors get the benefit of mixing high IOPs workloads with low IOPs workloads.
Say a cloud vendor needs a bunch of HDD for a database workload with high IOPs. Using modern disks (4+ TiB) this leaves a lot of stranded disk storage that can only be used for low IOPs workloads.
Archive storage uniquely meets the criteria of lots of storage, yet low IOPs.
Disclaimer work for Google but have no knowledge of how AWS glacier works.
- ggm 7y agoI could believe that we have a lot of unused space which is amenable to a different overlay use, but the potential for mis-design is huge here. If I pay high IOPs cost and you have to replace my high IOPS data backend on my paypoint, migrating the low paypoint secondary customer is non-trivial if not designed in day one (I am sure you did: cheap players might not understand the risk exposure here) The telco equivalent was ISDN, where a single linecard with two sub-rate ports might be sold to a bank, and a domestic user. The bank could (and would) demand card reset 24/7 to restore service to their ATM, the domestic user simply lost carrier, and game state.