Seagate flashes 60TB SSD monster

Seagate's shows off another two new SSD products: an 8TB NVMe drive, and a massive 60TB SSD demo in a 3.5-inch form factor at the Flash Memory Summit.

The 60TB shows what's possible if you cram more than a 1,000 Micron 3D NAND dice into a full-size, 3.5-inch disk form factor package. We understand it has dual port 12Gbit/s SAS interface and 150,000 random read IOPS, undisclosed write IOPS (suspect a relatively crap number). The sequential read/write numbers are 1.5 and 1.0GB/sec.

The drive has a single controller and we have no information about likely endurance. This would seem to be a precursor of an active (read several / write infrequently) archive SSD or some other application featuring read-intensive, latency-sensitive, high-capacity storage. Just 17 of these suckers would give you slightly over 1PB of capacity.

The 60TB is four times larger than Samsung's 15TB 3D NAND SSD, which gives Seagate bragging rights. The Samsung SSD has 512 x 256Gb 48-layer V-NAND chips stacked in 16 layers inside it.

Micron's 1100, announced in June, was its first 3D NAND M.2 drive using 384Gbit dice. Our rough math says you'd need 1,250 of them to build a 60TB drive.

Seagate's 60TB whopper is also six times larger than its own 10TB 3.5-inch disk drive. We don't know how many times more it costs than the disk and would love to see the $/GB figures for the 60TB SSD and the 10TB HDD.

Seagate suggests we could see a 100TB SSD in the future. If a product emerges, Seagate isn't indicating what it might be called. Mike Vildibill, Advanced Technologies and Big Data VP at HPE, offered a canned supporting quote: "Seagate's new 60TB SAS SSD offers an exciting possibility for customers to achieve higher server storage performance and capacity configurations never seen before." Looks like HPE could be signed up to use the thing.

Seagate says the 8TB Nytro XP7200 NVMe SSD will be available through channel partners by the end of the year. A 60TB SAS SSD product is anticipated for some time in 2017.

Share this post