Iometer - Disk Response

Version and / or Patch Used: 1.1.0

We use Iometer to measure disk response times. Disk response times are measured at an industry accepted standard of 4k QD1 for both write and read. Each test is run twice for 30 seconds consecutively, with a 5-second ramp-up before each test. The drive/array is partitioned and attached as a secondary device for this testing.

Write Response

Read Response

Average Disk Response

Just as we expected we would see, our MX200 array sets the bar with the lowest write response times of any 2-drive array to come across our test bench. Significantly faster than our MX100 array, which again shows the performance increase Crucial was able to exact from their newest SSD. Read response times are better than the MX100, but nothing like we see from Samsung's 850 Pro. Keep in mind that write performance is more important than read, and in that regard the MX200 is an absolute beast.

DiskBench - Directory Copy

Version and / or Patch Used: 2.6.2.0

We use DiskBench to time a 28.6GB block (9,882 files in 1,247 folders) of mostly incompressible random data as it's transferred from our DC P3700 PCIe NVME SSD to our test drive/array. We then read from a 6GB zip file that's part of our 28.6GB data block to determine the test drive/array's read transfer rate. The system is restarted prior to the read test to clear any cached data, ensuring an accurate test result.

Write Transfer Rate

Read Transfer Rate

Look at that, not only does our MX200 2 drive array roast the competition with far superior write transfer rates than any 2 drive array we've seen to date, it even manages to outperform our read-centric 850 Pro array with a better read transfer rate. We figured our MX200 array would deliver awesome transfer rates, but we didn't expect they would be this good.

We at TweakTown openly invite the companies who provide us with review samples / who are mentioned or discussed to express their opinion of our content. If any company representative wishes to respond, we will publish the response here.