Solid State Systems Sss6698bb Better [updated] Review

Solid State Systems SSS6698BB: Why This Controller is Better for Budget SSD Performance

In the crowded world of flash storage, most consumers focus solely on NAND chips (TLC, QLC, 3D NAND) or the end-brand (SanDisk, Kingston, TEAMGROUP). However, storage enthusiasts and data recovery specialists know the truth: the controller is the brain of the SSD. In the budget and value segment, one name has been gaining traction for offering a genuinely "better" balance of reliability, heat management, and speed: The Solid State Systems SSS6698BB.

If you are looking for an affordable SSD upgrade for an older laptop, a secondary game drive, or a USB bridge device, you have likely encountered the SSS6698BB. But is it actually better than the competition (like Phison S11 or Silicon Motion SM2258XT)? This deep dive explains why this specific controller architecture outperforms its price peers.

5. Power & Thermal Management

• Low active power (~0.5W typical)
• DevSleep / Slumber modes – Reduces power in idle states (good for USB & portable SSDs).
• Built-in thermal throttling – Prevents overheating under sustained writes.

3. Performance

• Sequential Read: up to 560 MB/s
• Sequential Write: up to 520 MB/s (depending on NAND)
• Random Read (4K): up to 75K IOPS
• Random Write (4K): up to 70K IOPS

1. Firmware tweaks (if possible)

• Use MPTool (Mass Production Tool) for SSS 6698BB to change settings:
  • Enable 更高的 ECC 强度 (stronger error correction) if flash is poor quality.
  • Switch between Fixed mode (removable disk) and HDD mode (local disk) — HDD mode sometimes allows better Windows disk management.
  • Increase LED activity blink (usability, not performance).
• Known tool versions: SSS MP Tool V2.175, V2.185, V2.198 (requires compatible flash DB).

3. File system & OS optimizations

• Format as NTFS or exFAT (not FAT32) to reduce metadata overhead.
• Disable indexing on the drive.
• Set “Better performance” in Windows device policy → enables write caching (but risk of data loss if unplugged).

2. The Gaming Secondary Drive

For Steam games that do not require DirectStorage (which needs NVMe), the SSS6698BB’s high random read performance means level assets load faster. It is better than a mechanical drive by 400x. solid state systems sss6698bb better

What is the Solid State Systems SSS6698BB?

First, let's demystify the name. Solid State Systems (often abbreviated SSS) is a Taiwanese controller design house. While they are not as famous as Phison or Marvell, they have dominated the bridge controller and low-cost embedded storage markets for decades. The SSS6698BB is their 6th generation, 4-channel, DRAM-less SATA III controller.

"DRAM-less" might sound negative, but the "6698BB" variant includes specific optimizations (namely HMB – Host Memory Buffer emulation and advanced wear leveling) that make it better than older DRAM-less designs. Solid State Systems SSS6698BB: Why This Controller is

1. The "Better" Performance Claim

Is the SSS6698BB "better" in terms of speed?

Verdict: It is average.

• Interface: It supports USB 3.0 (5Gbps).
• Typical Speeds: When paired with decent quality NAND flash memory (MLC or TLC), this controller typically yields read speeds of 80–120 MB/s and write speeds of 30–80 MB/s.
• Comparison: Compared to high-end controllers like the Phison PS2251-13 series or Silicon Motion SM3267, the SSS6698BB often falls short in write consistency. It is prone to speed drops once the SLC cache (if configured) is filled.

However, if you are comparing it to USB 2.0 controllers (like the SSS6690 or Alcor AU6989), the SSS6698BB is undeniably "better." It represents a significant generational leap in throughput, making it suitable for transferring large files (>1GB) where USB 2.0 would stall.

4. Firmware Stability: The “BB” Revision

The “BB” suffix is critical. The original SSS6698 (non-BB) had a bug where disconnecting the drive during a write would corrupt the entire partition table. The BB revision added a capacitor-backed write buffer. If you unplug the drive improperly, the controller finishes the last write operation using residual power. That is unequivocally better for data integrity. Low active power (~0