You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to write a binary file to NVMe SSD with highest speed possible. According to CrystalDiskMark results, a RAID0 Disk (8 NVMe SSDs) with 16TB capacity can give 16.5GB/s writing speed.
Then, I checked the CrystalDiskMark source code as a reference to improve write performance. I created a small trial project with CreateFile and WriteFile functions from C++ standard library to write 4MB of data 16 times sequentially and the speed I observed was just 150MB/s. On the contrary, writing 4MB of data 16 times using ofstream::write gave speed upto 4.5GB/s.
I'm now confused from my observations, whether I have interpreted your code to write faster is wrong or missed something important while using it. Kindly advice me with a small piece of example code (preferably in C++) to achieve maximum write speed in NVMe SSDs/RAID0 disks.
Thank you for your time.
Best regards,
Chaithra
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to write a binary file to NVMe SSD with highest speed possible. According to CrystalDiskMark results, a RAID0 Disk (8 NVMe SSDs) with 16TB capacity can give 16.5GB/s writing speed.
Then, I checked the CrystalDiskMark source code as a reference to improve write performance. I created a small trial project with CreateFile and WriteFile functions from C++ standard library to write 4MB of data 16 times sequentially and the speed I observed was just 150MB/s. On the contrary, writing 4MB of data 16 times using ofstream::write gave speed upto 4.5GB/s.
I'm now confused from my observations, whether I have interpreted your code to write faster is wrong or missed something important while using it. Kindly advice me with a small piece of example code (preferably in C++) to achieve maximum write speed in NVMe SSDs/RAID0 disks.
Thank you for your time.
Best regards,
Chaithra
The text was updated successfully, but these errors were encountered: