Storage provider Scality compares the power efficiency between high-density HDDs and QLC SSDs.
Firm Claims HDDs Can Use Less Power Than SSDs : Read more
Firm Claims HDDs Can Use Less Power Than SSDs : Read more
For each workload profile, drives are assumed to be in the specified power state for the percentage of time indicated.
Who cares? HDDs are SLOW and noisy. Unless I purposefully keep them spinning, they spin down and make a chatter when they are woken up. I have had several HDDs fail and only one early SSD. I get that they are trying to keep their business alive, but the only reason for HDDs is for large low access storage for less cost, and that is shrinking every year.
But the speed also affects the power draw. It's why utility companies measure in Kilowatt Hours, KwH. If your 5W per disk are being drawn for 20s instead of 1m, that's still an overall savings.If you run a cluster with i dont know, 128, 256, 512 HDD's large, 5W per disk is a big difference. Not everything is based around speed or required absolute speed.
It's right in the article:This is highly dubious. Which HDD models were compared to which SSD?
This. In datacenters, people talk about density all the time. So, I'm sure they mean power normalized by capacity.What do they mean by power density? energy per Mb,
Probably because HDD companies are starting to get a bit concerned about QLC SSDs encroaching into more HDD use cases and market niches.Why measure the power consumption of drives meant for different use cases under the same useless condition?
True. They should've adjusted the duty cycle estimates to account for the performance differences.If an SSD draws twice the energy but it does so in a quarter of the time, it's used half of the energy that the HDD would to do the same thing.
For an online storage provider, absolute speed of a single transfer stream or drive isn't much of a factor as most clients won't be accessing online storage at connection speeds that will pose any issue for HDDs, especially after software-RAID scattering data cross multiple drives for resiliency. They are more concerned about the overall cost of keeping a given amount of storage online.Simply calculating how many watts it takes to transfer 500 gigabytes of data would settle the issue.
Exactly.For an online storage provider, absolute speed of a single transfer stream or drive isn't much of a factor as most clients won't be accessing online storage at connection speeds that will pose any issue for HDDs, especially after software-RAID scattering data cross multiple drives for resiliency. They are more concerned about the overall cost of keeping a given amount of storage online.
Depends on what they are being used for. In the case of an online storage company, having thousands of customers reading and writing data striped across multiple drives means drives rarely are idle long enough to bother spinning down.Do hard drives go into a sleep mode when not accessed in data centers ?
In some "near-line" storage applications, I would expect so. Backups might be one example, but also data which is not expected to be accessed very frequently. I'm not speaking from any first-hand knowledge, however.Do hard drives go into a sleep mode when not accessed in data centers ?
Yes, good point about non-spinning HDDs.I can imagine that a great deal of archived data could be stored on "non-spinning" Iron very efficiently. Although probably SSD's in a "suspended" state should be able to do the same. A lot of stored data is rarely accessed.
I could imagine data either being sorted a priori or dynamically into a near-line storage tier. Something like backups or video surveillance might be good examples of cases where you know data is unlikely to be read. So, once you fill a drive with such data, you can explicitly spin it down, or just rely on an automatic spin-down based on the amount of time since last access.Depends on what they are being used for. In the case of an online storage company, having thousands of customers reading and writing data striped across multiple drives means drives rarely are idle long enough to bother spinning down.
The typical heuristic for scrubbing is usually about once per month. However, it'll take a few days, if you do it at full speed. Dual-actuator drives would cut that in half, but they're still far from the norm.Add data scrubbing during otherwise idle time to the mix to catch bit rot before it may cause data loss, I doubt HDDs get much down-time.
Or 100 times if it's highly random.It's doesn't mention what they consider a read. Is it the drive just reading the allocation?
Speaking to larger files, It will take an HDD probably three times longer to read the same sized file resulting in 3 times more power needed.
If you are building an online storage service, most of the storage will be idle most of the time even if it is only lowly HDDs.Sure, the only time I can see an SSD using more power is during writes, but they are so fast, the HDD will sit there and consume power for much longer as the SSD will sit there idle doing nothing because the task is already done.
The power draw the drive needs to spin up still far exceeds what an SSD will use waking up from idle or low power state, No matter how anyone looks at it, an SSD will always consume less, unless you look at the numbers at the right time and at the right work loads as such int he that link.If you are building an online storage service, most of the storage will be idle most of the time even if it is only lowly HDDs.
Not sure if some people skipped the article and went straight to the comments, but they took power usage directly from the drive manufacturer (Micron):Sure, the only time I can see an SSD using more power is during writes, but they are so fast,
Power Data Per Drive | SSD | HDD | HDD Advantage |
---|---|---|---|
Idle (watts) | 5 | 5.7 | -14% |
Active read (watts) | 15 | 9.4 | 37% |
Active write (watts) | 20 | 6.4 | 68% |
Read-intensive workload (avg. watts) | 14.5 | 8.7 | 40% |
Write-intensive workload (avg. watts) | 18 | 6.6 | 63% |
Power-density read-intensive (TB/watt) | 2.1 | 2.5 | 19% |
Power-density write-intensive (TB/watt) | 1.7 | 3.3 | 94% |