SK hynix to place custom tiny CPU cores in its SSD controllers to ease Arm load as drive speeds rocket
- ID
- 35412
- Status
- summarized
- Published
- 14 Oct 2026, 10:00 PM
- Fetched
- 15 Oct 2026, 12:08 AM
- Provider
- Tom's Hardware
- Category
- technology
- Original URL
- https://www.tomshardware.com/pc-components/ssds/sk-hynix-to-place-custom-tiny-cpu-cores-in-its-ssd-controllers-to-ease-arm-load-as-drive-speeds-rocket-each-h-tpu-reportedly-draws-2-5-percent-of-a-cpu-cores-power
- Source URL
- https://www.tomshardware.com/feeds/all
Summary
- Score
- 5.0
- Created
- 15 Oct 2026, 12:10 AM
- Tags
- Audience
- developersdatabase_learners
What happened
Tom's Hardware reports that SK hynix plans to embed its own small cores, called Hynix Transaction Processing Units (H-TPUs), into SSD controllers so that repetitive I/O work no longer has to run on general-purpose Arm CPU cores. Each H-TPU is described as using a four-stage, in-order pipeline, deployed in clusters, with management still handled by the traditional Arm CPU. SK hynix claims each H-TPU draws roughly 2.5% of a general-purpose CPU core's power and takes about 4% of its area, and reportedly intends to apply the design across its product portfolio, per TheElec.
Why it matters
There is no shipping product, part number, date, or performance benchmark in this text, so nobody should change a storage purchase, database config, or cloud instance choice because of it yet. The concrete thing to watch is the claim itself: 2.5% of a CPU core's power and 4% of its area for a core that only does routine I/O. If that holds up in real drives, the constraint on NVMe throughput shifts from controller CPU power toward the NAND and fabric, which is what would eventually show up in your read/write-per-watt numbers on dense storage nodes.
Discussion angle
This is the same pattern as DPUs and SmartNICs — offload repetitive work to small specialized cores and leave the general-purpose CPU for coordination. Worth asking live: if SSD controllers become heterogeneous SoCs with clusters of tiny in-order cores, does that change how you'd think about queue depth and parallelism tuning in your database, or is controller internals too far below the abstraction line to ever matter to application developers?