WD Purple 32GB

  • Obtained from: Amazon
  • Price paid: $13.04
  • Advertised capacity: 32GB
  • Logical capacity: 31,914,983,424 bytes
  • Physical capacity: 31,914,983,424 bytes
  • Fake/skimpy flash: Skimpy (0.27% skimp)
  • Protected area: 83,886,080 bytes
  • Adjusted skimp: 0.0035%
  • Speed class markings: Class 10, U1
  • CID data:
    • Manufacturer ID: 0x03*
    • OEM ID: 0x5344 (ASCII: SD)
    • Product name: 0x5758333247 (ASCII: WX32G)
    • Product revision: 0x80
Sample #123Average
Serial number0x81df12ba0x833f32f00x832f32f0N/A
Manufacture dateMar 2023Mar 2023Mar 2023N/A
Sequential read speed (MB/sec)84.9984.6584.9284.85
Sequential write speed (MB/sec)24.8521.1124.2023.39
Random read speed (IOPS/sec)2,025.241,959.762,014.111,999.70
Random write speed (IOPS/sec)395.16389.42403.68396.09
Read/write cycles to first errorNot yet determinedNot yet determinedNot yet determinedNot yet determined
Read/write cycles to complete failureNot yet determinedNot yet determinedNot yet determinedNot yet determined
Total days to complete failureNot yet determinedNot yet determinedNot yet determinedNot yet determined
Card reader usedJJS CR-UTC4ACJJS CR-UTC4ACJJS CR-UTC4ACN/A
Package frontN/A
Package backN/A
Card frontN/A
Card backN/A

* This manufacturer ID/OEM ID combination is pretty well known to be associated with SanDisk.

Discussion

I think this is one I found out about after perusing through SanDisk/Western Digital’s online store and seeing what options they had available. And since I seem to be reviewing everything else of SanDisk’s, why not add this to the mix?

Performance-wise, SanDisk set the bar pretty low on this one — there are no speed claims on the package, and the card itself only bears the Class 10 and U1 markings. It easily met the requirements for both of those markings. All performance metrics came within one standard deviation of average, with sequential write speeds being the worst of the four scores. Overall, it performed about as well as the Samsung EVO Plus 32GB.

All three samples are currently undergoing endurance testing:

  • Samples #1 and #2 have yet reached the 2,000 read/write cycle mark. They are expected to get there sometime in August 2024.
  • Sample #3’s first error was an address decoding error, affecting four sectors, during round 1,645. It has survived 1,830 read/write cycles in total so far.

Side note: All three samples did technically experience errors; however, I’m almost positive that these were device mangling errors and thus not the card’s fault. Therefore, I’ve decided to discard those errors. I’ve since added code to my program to detect and mitigate these types of errors.

July 5, 2024

Leave a Reply

Your email address will not be published. Required fields are marked *