0Fill – Samsung 970 EVO (PCIe 3.0x4) & 850 EVO (Sata)
*Sorry for an error on the original all ssds comp grid, where the Samsung sata was labelled "950 EVO" which of course should have been "850 EVO"... since a 950 EVO doesn't exist and its PRO variation is a nVME. To my pitiful defense there was a LOT of data and I really think Samsung are way overdue to change their monikers for their nVME and especially stop reusing the same numbers into a different series 2 years after...
Both drives overprovisioned the same, and filled with the same exact data – which is the original data that was already on the 850 EVO. Therefore in earlier runs I posted the Sata was 84% as it is here, but the nVME was overprovisioned and filled to better match with the SN850X 1TB I had tested.
Without further ado... the (corrected) all ssds comp grid, so that we have our reference at end. To clarify those were run with the Default (Random) Data Set.
Helpful here as I don't intend to make another one of these for the 0Fill especially since I cannot retest the SN850X, and especially since a new comp grid would only be useful if I expanded it to include the above and the 0Fill side by side. That's where I draw the line. Instead I'll use pictured of the CDM results in 0Fill and a reminder of what we "expected" based on the Default Data Set.
970 EVO 250GB 3.0x4
nVME Peak - expecting
3564/1507/1601 in SEQ128K and
1035/1531/1108 in RND4K
Default Peak - expecting
3567/1537/1819 in SEQ1M and
716/488/576 in RND4K
Real World Performance - expecting
2383/1538/1425 in SEQ1M and
71/210/78 in RND4K
850 EVO 250GB Sata
nVME Peak - expecting
555/520/480 in SEQ128K and 401/326/378 in RND4K
Default Peak - expecting
553/532/502 in SEQ1M and
401/362/378 in RND4K
Real World Performance - expecting
511/496/446 in SEQ1M and
37/149/60 in RND4K
Hmmmm... okay so we have outliers, but they go both ways - slower Default Data Set OR slower 0Fill Data Set. And they sort of disseminate at all places. Instead of considering it an effect of 0Fill, some elements make me suspicious. Therefore I must validate - in as trying to reciprocate results from both Data Set - for a few scores because they rather are illuminated for being out of place.
970 EVO outliers:
-in nVME Peak the 0Fill is much slower in RND4K Mix. Looking at the similar Reads and Writes with both Data Sets, the gap will surely close in validation.
-in Default Peak the Default Data Set was quite slower on all RND4K. That would SEEM to go in phase with what is "expected" of a 0Fill run but I'm very curious to validate.
-in Real World the Default Data Set was much slower on both Reads and Mix.. More or less goes with "expected" of a 0Fill... Writes would usually be the uplift instead of Reads. Curious to validate as well.
Let's not forget also that the 970 EVO on the first batch of test was filled around 6% instead of 84%. However my instinct is all the validations might close most of those gaps until we cannot speak of an outlier anymore, despite the huge difference in drive fill - it's too all over the place to sound like some form of scaling gained by not using random data sets.
850 EVO outliers:
-in nVME Peak the Default Data Set was quite slower in Writes. Looking at the similar Reads and Mix results with both Data Sets, the gap will most surely close in validation.
-in Real World the Default Data Set was quite slower in Reads. Again, looking at the similar Writes and Mix results with both, the validation shall prove it an outlier as well.
Going to validate these as I write this.
EDIT:
850 EVO outliers RECIPROCATED on a first run...
All concerned RND4K tests showed as to outline the consistency of ALL results there.
EDIT:
970 EVO plays it harder...
I could reciprocate easily all Default Peak RND4K outliers on the first run.
Not at all after two validation runs regarding the nVME 0Fill RND4K Mix scores... Still as low as posted in the first run.
And that is really weird. I'll try to validate the other way around with running a Default Data Set... cause I think the only sensible explanation is that I made an error when I filled the all SSDs comp grid.
Getting somewhat weirder, I more or less reciprocated the outliers for the Default Data Set Real World SEQ on first run... in that I got EVEN FASTER score than the 0Fill run by the same margin it was slower in the compilation grid... but still the same relatively slower Mix score.
So going full validation mode now on the 970 running nVME and Real World for both data sets a few times and see what I get.
FINAL EDIT
The ONLY explanation for the nVME RND4K Q32T16 Mix HUGE gap was a
HUGE error when filling my All SSDs compilation grid of earlier.
Otherwise, EVERYTHING that was problematic between 0Fill and Default Data Set is most strictly flatlining.
Real World SEQ tend to vary
a little bit especially towards the Mix, and yeah at times you might get a super boost in Reads like I proved with the first attempt at validation, but for this i7 7700K and yadda yadda core system, it seems obvious the SEQ1M Q1T1 Read target is 2500+ MB/s for a Write target of 1535+ MB/s and a Mix target of 1400+ MB/s. Writes very very consistent, but Read and Mix do get some wider variance.
0Fill nVME Peak vs Default Data Set nVME Peak:
0Fill Real World vs. Default Data Set Real World: