QSIZE= $(( $SIZE / 32 )) #Size of Q32Seq testsĮcho 'Defaulting to $TARGET for testing 'ĭRIVE= $(df $TARGET | grep /dev | cut -d/ -f3 | cut -d ' ' -f1 | rev | cut -c 2- | rev )ĭRIVEMODEL= $(cat /sys/block/ $DRIVE/device/model )ĭRIVESIZE= $(($(cat /sys /block / $DRIVE /size) * 512 / 1024 / 1024 / 1024 ))GBĮcho 'Configuration: Size: $SIZE Loops: $LOOPS Write Only Zeroes: $WRITEZERO

WRITEZERO=0 #Set whether to write zeroes or randoms to testfile (random is the default for both fio and crystaldiskmark) dd benchmarks typically only write zeroes which is why there can be a speed difference. The drive produced a best random write test result of 444,940 IOPS, a little shy of the official maximum of 450,000 IOPS.SIZE=1024 #Size of each test, multiples of 32 recommended for Q32 tests to give the most accurate results. Similarly using the Peak Performance profile to gauge the 4K performance of the drive we could confirm the official random read maximum of 460,000 IOPS with a test result of 466,033 IOPS. Using the more advanced CrystalDiskMark 8 in its default setting as well as the Peak Performance and Real World profiles saw the Sequential test results confirm the official 3,500MB/s reads and 3,000MB/s writes with the best results of 3,617MB/s and 3,190MB/s for reads and writes respectively.

We could also confirm the official Sequential performance figures for the drive, up to 3,500MB/s and up to 3,000MB/s for reads and writes respectively with a best test read performance of 3,618MB/s and writes of 3,199MB/s.ĬrystalDiskMark 8 Peak Performance profile. Looking at the two benchmark screens, it's clear that the in-house WD controller doesn't have a preference for the type of data it's being asked to handle. In the CrystalDiskMark QD32 T1 test, the Blue SN570 shows an improvement in read performance over the previous Blue SN550 but the older drive has the edge when it comes to writes. CrystalDiskMark is a useful benchmark to measure theoretical performance levels of hard drives and SSD’s.

Crystal disk mark test