- 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
- Manufacturer ID:
| Sample # | 1 | 2 | 3 | Average |
|---|---|---|---|---|
| Serial number | 0x81df12ba | 0x833f32f0 | 0x832f32f0 | N/A |
| Manufacture date | Mar 2023 | Mar 2023 | Mar 2023 | N/A |
| Sequential read speed (MB/sec) | 84.99 | 84.65 | 84.92 | 84.85 |
| Sequential write speed (MB/sec) | 24.85 | 21.11 | 24.20 | 23.39 |
| Random read speed (IOPS/sec) | 2,025.24 | 1,959.76 | 2,014.11 | 1,999.70 |
| Random write speed (IOPS/sec) | 395.16 | 389.42 | 403.68 | 396.09 |
| Read/write cycles to first error | 1,366 | 1,761 | 1,644 | 1,590 |
| Read/write cycles to complete failure | 3,063 | Not yet determined | Not yet determined | 3,063 |
| Total days to complete failure | 127 | Not yet determined | Not yet determined | 127 |
| Card reader used | JJC CR-UTC4AC | JJC CR-UTC4AC | JJC CR-UTC4AC | N/A |
| Package front |  |  |  | N/A |
| Package back |  |  |  | N/A |
| Card front |  |  |  | N/A |
| Card back |  |  |  | N/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:
- Sample #1’s first error was a two-sector wide address decoding error during round 1,367. It chugged along for quite some time without any further errors. During round 3,064, however, the USB hub — to which its card reader was plugged into — had issues and needed to be reset. When I plugged the hub back in, every other card on this hub immediately started working; however, this card wouldn’t respond to commands, giving us yet another example of a SanDisk card dying suddenly and without warning.
- Sample #2’s first error was a two-sector wide address decoding error during round 1,762. It has survived 3,292 read/write cycles in total so far.
- Sample #3’s first error was an address decoding error, affecting four sectors, during round 1,645. It has survived 4,055 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.
October 2, 2024 (current number of read/write cycles is updated automatically every hour)