Memory and Storage for SI

Memory and Storage for SI, Part 6: The Capacity Drives

What 122TB to 300TB QLC drives do in an SI cluster, why bigger drives write in bigger pieces, and how to read their endurance and hard drive comparisons.

On this page 7 sections

The largest SSDs now hold about 245TB each. Micron’s 245TB 6600 ION is available today, Kioxia’s LC9 reaches 245.76TB, and Sandisk said its 256TB UltraQLC drive would come in the U.2 form factor in the first half of 2026. All of them store four bits per cell, in quad-level cell (QLC) flash, and all three makers pitch them at SI clusters.

Memory and Storage for SI, Part 6: a capacity SSD with a stack of QLC dies, a large unit with a small write landing in it, and a short row of SSD racks beside a longer row of hard drive racksA three-panel schematic. Left: a stack of thin QLC dies sits above an SSD board with flash packages and gold connector fingers. Center: one large unit drawn as four slots, with a small write landing in the first slot along a copper arrow. Right: a short row of SSD racks beside a longer row of hard drive racks, all the same size.GUIDE / MEMORY AND STORAGE FOR SI, PART 6Built for capacityDIES · UNITS · RACKS01 DIES02 UNITSunit rewritten03 RACKSSSD racksHard drive racks

Part 4 and Part 5 covered the fast end of an SI cluster’s storage, which means drives tuned for small reads and a tier that holds the KV cache. This part is about the other end, where most of the bytes sit, and asks what these drives are for and what they give up to hold that much.

What makes a drive this large

Capacity comes from the flash die and how many fit in one package. Kioxia builds the LC9 from 32-die stacks of 2Tb QLC dies, made with the logic bonded straight onto the memory array (CMOS directly bonded to array, or CBA). Micron’s 6600 ION is built on its ninth-generation G9 QLC with six planes per die, and Solidigm’s D5-P5336 on 192-layer QLC, every one of them at four bits per cell.

What makes a drive this large

Capacity drives reach 245TB, and Everpure’s modules 300TB

Bars start at zero; each bar carries its own basis

A horizontal bar chart of rated capacity per drive or module in terabytes, from zero to 300. Solidigm’s D5-P5336 reaches 122TB. Kioxia’s LC9 and Micron’s 6600 ION each reach 245.76TB. Sandisk’s UltraQLC is planned at 256TB. Everpure’s DirectFlash Module is reported at up to 300TB by Computer Weekly. Solid teal bars are maker ratings, the dashed teal bar is a maker plan, and the dashed neutral bar is a reported figure.Drive or module0100200300Rated capacity per drive or module, TBSolidigm D5-P5336122TBKioxia LC9245.76TBMicron 6600 ION245.76TBSandisk UltraQLC256TBEverpure DirectFlash Module300TBMaker ratingMaker planReported
Figure 6.1 · Solidigm, Kioxia and Micron rate their drives, Sandisk plans a 256TB drive, and Computer Weekly reports 300TB Everpure modules. Source: Solidigm, Kioxia, Micron and Sandisk releases; Computer Weekly.

Capacity per drive has doubled in steps. Solidigm introduced the 122TB D5-P5336 on November 13, 2024. Kioxia added its 245.76TB LC9 on July 21, 2025, beside a 122.88TB model, and Micron made the 245TB 6600 ION available on May 5, 2026.

Everpure (Pure Storage until February 23, 2026) is one maker that skips the drive format altogether and builds its own flash modules for its arrays, and they now reach up to 300TB, according to Computer Weekly. Flash Foundations Part 1 covers the bays and form factors that hold the standard drives.

Where they sit in an SI cluster

The makers describe the jobs in their own terms. For Kioxia, they are storing datasets for training large language models, and building the embeddings and vector databases that retrieval augmented generation (RAG) reads during inference. Sandisk aims its 256TB drive at data ingest, preparation, and fast SI data lakes. Micron frames it as a limit on the building: SI pipelines, analytics platforms, and object storage are growing faster than power, cooling, and space budgets allow.

Where they sit in an SI cluster

Capacity drives hold the data SI writes once and reads often

The fast end of the cluster, the KV cache, uses a different drive

A left-to-right pipeline. Ingest feeds Preparation, which feeds a large teal box, a data lake on capacity QLC drives. Two copper arrows leave the data lake: one to Training reads and one to Embeddings and vector databases for RAG. Below the pipeline, a chip states that enterprise SSDs were 48% of NAND shipments in Q2 2026, up from 26%. Under that, set apart with a dashed border, the KV cache tier from Part 5 uses a TLC drive rated at 3 drive writes per day.01 THE DATA PATHIngestPreparationData lake oncapacity QLCdrivesTraining readsEmbeddings andvector databasesfor RAG02 THE DEMANDEnterprise SSDs: 48% of NAND shipments in Q2 2026, up from 26%03 THE FAST ENDKV cache tier (Part 5): TLC drive, 3 DWPDCapacity QLC drivesOther stepData flowSeparate tier
Figure 6.2 · Data is ingested, prepared and kept on capacity QLC drives, then read by training and by retrieval, while Part 5’s cache tier runs on TLC. Source: Kioxia and Sandisk releases; Micron blog; Counterpoint Research; StorageReview on Kioxia CM9.

Read together, those jobs suggest a read-heavy pattern. Data arrives in large pieces and then gets read many times, by training runs and by retrieval.

Demand has moved fast. In Counterpoint Research’s count, SI inference drove enterprise SSDs to 48% of global NAND shipments in Q2 2026, nearly double the 26% share a year earlier. That count covers every enterprise SSD, the fast ones included, so it is a measure of the whole server market rather than of capacity drives.

Part 5’s KV cache tier wants a different drive. Kioxia’s pick there is its CM9, a triple-level cell (TLC) drive rated at 3 drive writes per day (DWPD).

Bigger drives write in bigger pieces

An SSD finds data through a map from the addresses the host uses to the places the flash holds them, and Flash Foundations Part 6 explains why it needs one. Each map entry covers one indirection unit (IU). With 4-byte entries and a 4KB unit, the map is about 0.1% of the drive’s capacity, and the drive keeps it in DRAM. For a 122.88TB drive that is about 120GB of DRAM. With one entry per 32KB it is an eighth of that, about 15GB.

Bigger drives write in bigger pieces

A 4KB write into a 16KB unit rewrites the whole unit

Schematic; the two map bars are drawn to scale

Three numbered bands. In 01, aligned, one 16KB unit is drawn as four 4KB slots and a single 16KB write fills all four, so the unit is written once. In 02, a small write, one 4KB write lands in a 16KB unit: the drive reads the 16KB unit, modifies 4KB and writes 16KB back, which is read-modify-write. For 4KB random writes Micron rates 0.3 drive writes per day on a 4KB unit and 0.075 on a 16KB unit. In 03, the map, two bars for a 122.88TB drive: one entry per 4KB takes about 120GB, and one entry per 32KB takes about 15GB, about an eighth as much.01 ALIGNED16KB unit4KB4KB4KB4KBone 16KB writewritten oncethe write fills the unit02 SMALL WRITE16KB unit4KBread the 16KB unitmodify 4KBwrite 16KB backread-modify-write4KB random writes: 0.3 DWPD on a 4KB unit, 0.075 on a 16KB unit03 THE MAP122.88TB driveone entry per 4KB: about 120GBone entry per 32KB: about 15GBSlot in useIdle slotWrite and read-back
Figure 6.3 · A write that fills the unit is written once, a smaller write makes the drive read and rewrite the unit, and a larger unit shrinks the map. Source: Solidigm; Micron 6600 ION product brief; map arithmetic at 4 bytes per entry from Flash Foundations Part 6.

So larger drives map larger units. In Solidigm’s description, QLC drives use an indirection unit of 8KB to 64KB, one that grows with capacity. Its D5-P5336 uses 16KB on most models and 32KB on the 122.88TB model. Micron’s 6600 ION uses 4KB on the 30.72TB model and 16KB on the three larger ones.

Small writes carry that cost. A write smaller than the unit, or one that does not line up with it, makes the drive read the whole unit, change part of it, and write it all back. Solidigm calls that read-modify-write the main cause of higher write amplification, and notes that host software is generally tuned around 4KB writes.

Micron’s ratings put a number on it. The 30.72TB model has a 4KB unit and is rated at 0.3 DWPD for 4KB random writes, and the 16KB models at 0.075. That is a quarter as much. Across those two models the ratio matches the unit size over the write size, and 16KB / 4KB is 4. Writes that fill the unit don’t pay it, and the same 16KB models are rated at 0.3 DWPD for 16KB random writes and 1.0 for 128KB sequential writes.

Sandisk takes another route on the write path. It says its UltraQLC platform writes straight to QLC with no SLC buffer, and each write is safe against power loss on its first pass.

Endurance, read in petabytes

A DWPD figure looks small on these drives because it multiplies a very large capacity. Solidigm rates the D5-P5336 at 0.42 to 0.60 DWPD over five years, rising with capacity, and at 5.9PB to 134.3PB written across the same models. For the 122.88TB model, 122.88TB × 0.60 × 365 × 5 comes to about 134.6PB, close to the rated 134.3PB.

Endurance, read in petabytes

Below one DWPD still comes to 134.3PB on a 122.88TB drive

0.42 to 0.60 DWPD across the same models

A vertical bar chart of rated petabytes written over five years for the five Solidigm D5-P5336 capacities, from zero to 160. The 7.68TB model is rated at 5.9PB, the 15.36TB model at 14.7PB, the 30.72TB model at 32.1PB, the 61.44TB model at 65.2PB and the 122.88TB model at 134.3PB. Across the same models the drive writes per day rating runs from 0.42 to 0.60.Rated petabytes written over five years, PB040801201605.9PB7.68TB14.7PB15.36TB32.1PB30.72TB65.2PB61.44TB134.3PB122.88TBD5-P5336 capacitySolidigm rating
Figure 6.4 · Solidigm rates the D5-P5336 at 5.9PB to 134.3PB written over five years, rising with capacity. Source: Solidigm D5-P5336 product brief.

Those ratings carry their conditions. Solidigm rates the 16KB models with 16KB random writes and the 122.88TB model with 32KB random writes, so each figure assumes writes that fill the indirection unit, and the Micron numbers above show what smaller writes do to that budget. The same brief rates power-off retention at 3 months at 40°C, which is the figure to check before a drive goes on a shelf.

On client drives the worry about QLC wear is a separate question, and Flash Myths tests it on my own bench.

Against the hard drive: what the maker math shows

Micron’s brief sets a 245.76TB 6600 ION at 30W against a 44TB hard drive at 10W, which works out to 8.2TB per watt against 4.4. For 1EB of data Micron counts 4.7 racks of its drives at 212.3PB per rack against 31.5 racks of hard drives at 31.7PB, with 48 U.2 drives in each 2U server.

Against the hard drive: what the maker math shows

Micron counts 4.7 racks of SSDs against 31.5 of hard drives for 1EB

Micron’s assumptions for 1EB; every rack is drawn the same size

Two panels for 1EB of data. On the left, 245.76TB SSDs: five rack outlines in a row, the fifth shaded to about 70 percent of its height, labeled 4.7 racks at 212.3PB each. On the right, 44TB hard drives: thirty-two rack outlines of the same size in four rows of eight, the last shaded to half its height, labeled 31.5 racks at 31.7PB each. Below, the power figures: 8.2TB per watt at 30W for the SSD and 4.4TB per watt at 10W for the hard drive.01 245.76TB SSDS4.7 racks at 212.3PB each8.2TB per watt at 30W02 44TB HARD DRIVES31.5 racks at 31.7PB each4.4TB per watt at 10WSSD rackHard drive rackLast rack, partly full
Figure 6.5 · These are Micron’s assumptions, not a measured comparison: 4.7 racks of SSDs against 31.5 racks of hard drives, and 8.2TB per watt against 4.4. Source: Micron 6600 ION product brief.

Solidigm’s figures for its 122TB drive are up to 84% less storage power in network-attached storage than hard drives paired with TLC flash, and up to 4PB per rack unit.

These comparisons set the SSD’s rated maximum power against a typical rating for the hard drive, and they measure the budgets Micron says are being outgrown: power, cooling, and floor space. The rack count is the most useful of them for planning floor space, and none of these documents gives a price per terabyte for either side, so a buyer has to bring that number to the comparison.

DirectFlash: the map moves to the array

Everpure moves most of the drive firmware into the array. Its DirectFlash Modules need no embedded controller doing the usual SSD work, because most of the tasks SSD firmware does move into the Purity operating system on the array’s own controllers, which maps the flash in every module. The modules also carry no DRAM of their own, and the array’s DRAM is shared across all of them.

DirectFlash: the map moves to the array

DirectFlash keeps one flash map in the array for all modules

Schematic; a module is flash and a simple controller

Two panels. On the left, a standard SSD: an outline with a controller, its own DRAM that holds the map, linked by a copper line, and a row of NAND packages, with gold connector fingers along the edge. On the right, DirectFlash: an array controller box labeled Purity, one map, shared DRAM, joined by copper lines to four modules. Each module holds only a simple flash controller and NAND packages, and no DRAM.01 STANDARD SSDControllerDRAMthe mapNANDNANDNANDthe map sits in the drive’s DRAMA map in every drive02 DIRECTFLASHPurity: one map,shared DRAMCtrlNANDNANDCtrlNANDNANDCtrlNANDNANDCtrlNANDNANDno DRAM in any moduleOne map in the arrayNANDController or DRAMMap link
Figure 6.6 · A standard SSD holds its map in its own DRAM, while a DirectFlash array holds one shared map in its controllers’ DRAM. Source: Pure Storage (Everpure) blog, Escaping the SSD Trap, Part 2.

That moves the map problem from the third section out of the drive. A module’s capacity no longer has to come with its own map memory, because the array holds one view of all its flash.

DirectFlash has buyers among the largest operators. Everpure’s first hyperscaler deal was with Meta in late 2024, in Computer Weekly’s report, and on August 10, 2026, Everpure announced a design win with a second top-five hyperscaler. It expects that deal to add significant revenue starting in its fiscal year 2028.

What to watch

Sandisk’s August 2025 release put its 256TB U.2 drive in the first half of 2026, and none of the sources saved for this page confirms it went on sale, so that is the first thing to check. Everpure expects revenue from its second hyperscaler deal starting in fiscal 2028, and the size of that order will show whether arrays that manage raw flash spread past the largest operators.

What to watch

Capacity drive dates, from 122TB in 2024 to Everpure’s 2028 plan

Ordered by date, not to scale

A vertical timeline of seven entries, not to scale. Filled marks are dated events: November 13, 2024, Solidigm introduces the 122TB D5-P5336; July 21, 2025, Kioxia adds the 245.76TB LC9; February 23, 2026, Pure Storage becomes Everpure; May 5, 2026, the Micron 245TB 6600 ION is available; and August 10, 2026, Everpure announces its second hyperscaler deal. Hollow marks are plans: the first half of 2026, when Sandisk’s 256TB U.2 drive was due, and fiscal 2028, the open end, when Everpure expects revenue from that deal.November 13, 2024Solidigm 122TB D5-P5336July 21, 2025Kioxia 245.76TB LC9February 23, 2026Pure Storage becomes EverpureFirst half of 2026Sandisk 256TB U.2 duea planMay 5, 2026Micron 245TB 6600 ION availableAugust 10, 2026Everpure’s second hyperscaler dealFiscal 2028revenue Everpure expects from itopen endDated eventPlan or expectationTime
Figure 6.7 · Five of these have happened; Sandisk’s 256TB drive is a plan, and Everpure’s revenue from its second hyperscaler deal is an expectation. Source: maker releases.

The trend I’d watch is the indirection unit. In Solidigm’s account it grows with capacity, and host software that writes 4KB at a time pays more for each step up. My read is that capacity drives keep the read-mostly jobs, datasets and data lakes, and that anything writing in small pieces stays on TLC drives like the one in Part 5.

The series turns next to the five-minute rule, which asks how often data has to be read to earn a place in faster memory.

KEEP GOING / NEXT CHAPTERContinue to Part 7

Sources

Primary is the original paper, standard or datasheet. Secondary is a review, a vendor summary or a news report. Measured is my own test data.

Show all 15 sources, 12 primary