SP Superior 128GB

  • Obtained from: Amazon
  • Price paid: $10.97
  • Advertised size: 128GB
  • Logical size: 124,383,133,696 bytes
  • Physical size: 124,383,133,696 bytes
  • Fake/skimpy flash: Skimpy (2.83% skimp)
  • Protected area: 134,217,728 bytes
  • Adjusted skimp: 2.72%
  • Speed class markings: U3, V30, A2
  • CID data:
    • Manufacturer ID: 0x9f
    • OEM ID: 0x5449 (ASCII: TI)
    • Product name: 0x5350434320 (ASCII: SPCC )
    • Product revision: 0x20
Sample #123Average
Serial number0x959900780xd599007bNot yet testedN/A
Manufacture dateMar 2024Mar 2024Not yet testedN/A
Sequential read speed (MB/sec)90.1689.70Not yet tested89.93
Sequential write speed (MB/sec)30.4228.58Not yet tested29.50
Random read speed (IOPS/sec)2,259.442,238.06Not yet tested2,248.75
Random write speed (IOPS/sec)238.91240.29Not yet tested239.60
Read/write cycles to first error2,030Not yet determinedNot yet tested2,030
Read/write cycles to 0.1% failure threshold2,030Not yet determinedNot yet tested2,030
Read/write cycles to complete failure2,030Not yet determinedNot yet tested2,030
Total days to complete failure146Not yet determinedNot yet tested146
Card reader usedJJC CR-UTC4ACJJC CR-UTC4ACNot yet testedN/A
Package frontNot yet testedN/A
Package backNot yet testedN/A
Card frontNot yet testedN/A
Card backNot yet testedN/A

Discussion

After the disappointing results from the SP Elite, I wanted to know if Silicon Power was the issue, if the SP Elite was the issue, or if 3D NAND in general was the issue. To try to narrow down the issue, I picked up these cards and the SP Superior Pro 128GB.

I only have performance results from a single card at the moment…but just based on those results, it looks like this card is going to be slightly better than the SP Elite. Sequential read and random write speeds were similar, while sequential write and random read speeds were improved — about 40% better in sequential write speeds, and about 80% better in random read speeds. In terms of overall performance, this puts it just slightly above average.

On the endurance testing front:

  • Sample #1 was doing just fine until it got to round 2,031, when it began experiencing a couple of I/O errors. After just the second reset attempt, it stopped responding to commands altogether.
  • Sample #2 has not yet reached the 2,000 read/write cycle mark. It is currently expected to get there sometime in May 2025.
  • Sample #3 is still in the package, waiting to be tested.

January 5, 2025