Thursday, August 11th 2016
Samsung Unveils Massive 32 TB SSD Leveraging 64-layer 3D V-NAND
At the 2016 Flash Memory Summit, Samsung unveiled a massive 32-terabyte solid state drive (SSD) for enterprise applications. The drive leverages the company's 4th generation, 64-layer 3D V-NAND flash memory, making it the company's highest-capacity SSD, upping the 15.36 TB drive the company unveiled in March, 2016. The drive is built in the 12 mm-thick, 2.5-inch form-factor, and features the SAS 12 Gb/s interface. At the summit, the company announced that it plans to have 100 TB SSDs ready by 2020.
Source:
PC World
14 Comments on Samsung Unveils Massive 32 TB SSD Leveraging 64-layer 3D V-NAND
On a different note, if they can produce drives with such a huge capacity, why aren't any "normal" size drives in the offers for reasonable prices, like 1,2,3 or 4 TB?
BTW, Seagate released a 60TB drive on the same day:
technology.inquirer.net/50843/60tb-ssd-unveiled-by-seagate-at-flash-memory-summit-conference
Seagate's 60TB is 3.5" though, so the Samsung is a little better physical space-wise and two would be 64TB. :)
No? I thought as much. Fact is, NAND isn't particularly overpriced, not even in the enterprise space - it just scales linearly with capacity. True, you can get real cheap drives at 20c per GB, but then you're not getting as good a controller+firmware combo. M.2 is fundamentally limited in it's capacity to 8 NAND packages (4-6 if you demand full power-loss protection as the capacitors eat up the space) right now due to space constraints, and that's not changing anytime soon, so no, you can't just magically make magically reach parity with the 2.5" and 3.5" drives on M.2.
Capacities will grow.. maybe a 2TB M.2 drive this year, but 2.5" (and to a lesser extent 3.5") is where the real big drives will come.
These demonstrations of power tell you how dense and available these just are.
It's time. We had enough from the wd Seagate cartel of hdds
Fact is, the consumer market on the whole isn't willing to pay for it, so nobody produces it. Simply because they can't afford it (small outfits like PNY, Corsair and such), or the really big guys (Intel, Micron, SanDisk) don't care for it cause servers are way more lucrative. Samsung is the exception that pushes that far, because they can afford the relatively small loss on the consumer-side (basically a tiny amount of R&D in tweaking their firmware for consumer loads and managing a few extra SKUs) in exchange for market visibility.
In 2-3 more years, sure, you'll have your 2-4TB SSDs for consumers, but right now 480GB and 240GB is where the numbers are made, and 1TB is kindof up and coming.
EDIT: To add on that, up until very, very recently (48-layer stacked NAND), it was literally impossible to build drives over 1TB in the 2.5" 7mm form factor because one simply could not fit enough packages in the volume. This all changed a year ago for Samsung, and right about now for the rest of the industry.
The first step is to cram it in, the next to lower the price to end users. It may not take 2-3 years, the amount of data people need to store seems to only be growing, I'm sure 4K video will fuel that too once we see more content and 4k action cams etc. appear.
As for video, most consumers won't care, or will do a small jump to a bigger external HD. For the vast majority, it'll go to the cloud then be deleted from local storage.
For the few of us professionals and prosumers, we'll just have to suck up the pricing of real server gear.
I'd love it if things changed to massive local storage, but like many, I've kinda given up and resigned myself to effectively building and running my own personal cloud instead - associated costs and all.
It'll be interesting to see what things will look like with e.g. a single xpoint (or similar tech from someone else) package in a year or two,
EDIT: on the subject of XPoint, we just won't see them in the cheap SATA parts, and I doubt at anything less than 4x the cost of NAND, which makes the entire argument moot. Would be great as a caching layer in front of all-flash arrays though...