Phison has launched new SSD PCIe 6.0 controllers and is demonstrating working drives built on them

Phison has launched new SSD PCIe 6.0 controllers and is demonstrating working drives built on them

104 hardware

Phison debuts new SSD controllers at Computex 2026

At the Computex 2026 exhibition, Phison introduced several new controllers and finished drives that promise to change the PCIe‑SSD market.

What was shownKey specificationsPhison X3 (8‑channel)• PCIe 6.0 bus support
• Host interface PCIe x4
• NVMe 2.3, including on‑drive computing
• Read/write speeds up to 28 GB/s (double the speed of PCIe 5.0)
• 6.8 million IOPS at 4 KB blocksPhison E37T• Transition from the E27T model
• Target market – consumer SSDs without DRAM (PCIe 5.0)
• Read up to 14.9 GB/s, write up to 13.2 GB/s (typically achieved only with DRAM)
• 3 million IOPS at 4 KB blocks
• Power consumption ≤ 2.3 W → no active coolingPascari D201E• Form factor E1.S (from 1.6 to 15.36 TB)
• NVMe 2.1 + on‑drive computing
• Read/write up to 14.8 GB/s, IOPS up to 3.3 millionPascari X202Z• Form factor U.2 (thickness 15 mm)
• PCIe 5.0 2×2
• Same capacity and speed as the D201E Pascari D250P• E1.S enclosure (9.5 mm) – capacities from 480 GB to 3.84 TB

What this means for the market
- PCIe 6.0: The X3 controller promises almost double the read/write speed compared to current PCIe 5.0 drives and is already ready for release in 2027–2028.

- No‑DRAM SSDs: The E37T demonstrates that high speeds can be achieved without DRAM, and its low power consumption makes it attractive for laptops and compact systems.

- Enterprise solutions: Pascari continues to develop its NVMe 2.1 lineup with on‑drive computing support, offering both high‑capacity (D201E) and more compact options (X202Z, D250P).

Phison also showcased reference SSDs in new E3.S and E1.S form factors, confirming the flexibility of their platform for various applications.

Comments (0)

Share your thoughts — please be polite and stay on topic.

No comments yet. Leave a comment — share your opinion!

To leave a comment, please log in.

Log in to comment