For interest I have repeated the 4K Write Saturation Test on a Vector 256GB using our Oakgate Test Unit. Here are the results, firstly - allowing writes to 60% of the LBA (i.e. with a large additional OP) and secondly - allowing writes to 100% of the LBA (i.e. no additional OP)
Interestingly this shows that a steady state has not quite yet been reached after 45 minutes. It also shows that the IOPS norm has not fallen below 60k - but still significantly faster than the 44K you are observing. I suspect the differences between what we see on the Oakgate test Unit and the results observed in our article’s Windows based tests can be explained by the Intel RST driver and its caching capabilities.
You’ll also notice that a regular, temporary dip in IOPS can be clearly seen. I suspect that this is where the controller is quickly moving data from ‘Performance NAND’ to ‘Storage NAND’ (which is a feature of recent Indilinx firmware) to free up Performance NAND to accommodate further writes.
You can see here that even with no additional OP steady state has not been achieved after 45 minutes when tested in the Oakgate Unit.
I should have tested for longer
An observation raidlover - I warmly welcome people challenging our test results (it is very healthy) but perhaps a challenge that is used with absolute assertions such as ‘invalidates, widely skewed and/or not reproducible’ should first be considered more carefully.
Kind regards, Jeremy