3 ms·
Makes me wonder something Database machines are usually never shut down. And when they are, it's usually a manual process (unless we're talking about a power f
by raverbashing 13y ago
Makes me wonder something
Database machines are usually never shut down. And when they are, it's usually a manual process (unless we're talking about a power failure or something)
"Diesel generators, for instance - what's the use?"
Backup power (not only for Glacier).
Reducing power consumption in peak hours is a good strategy, however, I'm not sure how worried Amazon is about this (and the difference in price between regular hours and peak hours)
- reitzensteinm 13y agoIt's not about the price they're paying for power (peak hours from the power company's perspective), it's about the peak usage of their data center. As the article (correctly) says, the capital costs are dependent on your peak usage. If you have 1000 servers using 400kW at peak, you need sufficient air conditioning to extract 400kW worth of heat, and backup generation capable of producing 400kW. It doesn't matter if you only use 100kW 16 hours a day - the capital costs are the same. I'm suggesting that Glacier could live entirely in non peak periods, meaning that the capital costs are unchanged and the demand curve is flattened.
- raverbashing 13y agoThe real question then is: is there really a peak hour for datacenter usage/consumption? What's the consumption difference between peak and regular hours (and low-demand hours) How much power does Amazon use during mornings compared to Netflix watching peak time?
- keypusher 13y agoYes, I'm sure there is. Look at Google clicks by hour or similar metrics, there is a significant curve during the day, peak can be 4-5x the low.
- jpalomaki 13y agoI think the requirements for power are much different in case of glacier that with some more generic computing. With a service like glacier, running on hard disks, you could probably completely turn off large parts of your infrastructure. With 5 hour read latency there should be plenty of opportunities to optimize the reads so that only a small part of the infra needs to be powered on at any time. Also you might be able to skip the backup power part completely. The data is anyways distributed to few locations. The probability of many of them losing to power at the same time for several hours is likely to be very small. Maybe there's also large differences in how the customers use the system. I would assume some customers are more likely to retrieve data than others. Once you start learning these patterns you could further optimize the storage. The pricing of Glacier is not necessarily driven by technical reasons. Amazon already has S3 and they need to differentiate the products.