Synthetics are a great way to really break out the big numbers once in a while. We will see later how well this works in reality with the real application benchmarks. Therefore, I start with the CrystalDiskMark and four different file sizes. The SSDs were no longer new at the time of the test and I also had fill levels of plenty of 50% before deleting the data several times. The good thing is that the maximum values can still be reached safely after several tests and quite impressive numbers can be achieved.
You can see very well that the dynamic pSLC does exactly what it is supposed to, mind you with an empty (though not virgin) SSD. The nice thing about the 2 TB SSD is that there is a lot of space left and you should therefore never fill it more than 2/3 with data. A higher load does not affect reading, but the dynamic SLC will certainly reach its limits at some point during writing. And if you do it over and over again, switching the memory modules between the two methods will also eventually become impossible.
ATTO is very interesting this time, although I’m only working with two sizes here, which ends up being the same. Only the program knows where the 6 GB/s read rates are supposed to come from, while the write rates are more likely. Therefore, synthetic benchmarks of this kind should rather not be taken that seriously, especially when the firmware might also have been optimized for such benchmarks. But I did not want to deprive you of this result. In case who wants to show off. 😀
Video streams
But what happens when you stream a video? For this purpose, the industry uses the AJA benchmark, which is in effect an interface between synthetic benchmarks and practical application. The Corsair MP600 GS doesn’t fluff here either, even though it already deviates a bit from the theoretical write and read rates. We see that the comments made on the previous page about the dynamic pSLC cache and the behavior with the larger file blocks are completely true. Smaller file movements would be even faster if you leave out the overhead of the file system.
BENCHMARK-TABLE
6 Antworten
Kommentar
Lade neue Kommentare
Veteran
Neuling
Urgestein
Veteran
Mitglied
Neuling
Alle Kommentare lesen unter igor´sLAB Community →