How to recover Samsung 980 PRO TurboWrite Performance in a Windows Environment
Written by Support Team
Updated at February 25th, 2021
- Tutorial Videos & Installation Guides
-
FAQ
FnL Product Line Determining PCIe lane assignment for your SSD7000 Controller MacOS Windows Linux SSD6200 Series Controller SSD7000 Series Controller RocketStor Series RocketRAID Series RocketU Series Motherboard Compatible Report Other Questions Standard Responses for Known Issues or Subjects WebGUI eStore Gen5
- HPT
- Compatibility Reports
- FAQ
- Workaround Issue
1. Test Background
Samsung officially states that the sequential write performance of Samsung 980 Pro 1TB SSD’s, after exhausting the smart TurboWrite buffer, is 2000MB/s.
We conducted a series of tests to verify these specifications, and to identify ways to restore Turbo Wrote performance to an array comprised of Samsung 980 PRO SSD’s. Customers can follow the procedure outlined below to test their configuration.
2. Test System:
System |
GIGABYTE X570 AROUS MASTER |
CPU |
AMD Ryzen 9 3900X 12-Core Processor |
Memory |
32GB |
OS |
Win 10 64bit |
Adapter |
SSD7505 |
Disk |
Samsung 980 PRO 1TB *2 |
Tool |
IOmeter1.1.0
|
Test Script |
|
3. Test Procedure
TurboWrite maximum test:
a. Connect 2x Samsung 980 PRO SSD’s to the SSD7505. IOMeter will be used to test performance with a Windows 10 system, (RAID 0 comrised of 2x NVMe SSD’s), using a 2M-Seq-Write script.
b. Use Iometer to test and set different Maximum Disk Size values to determine the TurboWrite buffer size of the Samsung 980 PRO SSD.
c. Maximum Disk Size calculation formula: Using a 6GB write session as an example;
6GB=6*1024*1024*1024/512B=12582912
IOmeter Settings：
4. TurboWrite Performance Recovery Time Test
a. For Write data that is greater than the maximum value of TurboWrite, but not more than 70% of the total capacity:
Wait for 40/50/60min; this will will restore Turbo Write to the default value (full performance)
5. Test Results
a. TurboWrite maximum value:
Queue Depth=64 |
Data Pattern (Maximum Disk Size) |
2M-Seq-Write(MB/s) |
|
RAID0 with 2 NVMes (2worker) |
12GB (25,165,824) |
10029 |
216GB (452,984,832 |
10012 |
|
220GB (461,373,440) |
10017 |
|
221GB (463,470,592) |
10015 |
|
222GB (465,567,744) |
4004 |
|
224GB (469,762,048) |
3898 |
|
228GB (478,150,656) |
3812 |
b. TurboWritePerformance Recovery Time
|
RAID0 with 2 x NVMe SSD’s (1worker) First test session: 120G Second test session: 111G | ||
Test Session (40 Min) |
Performance (MB/s) |
Screenshot (IOMeter) |
1 |
3848 |
|
2 |
3972 |
|
Test Session (50 Min) |
Performance (MB/s) |
Screenshot (IOMeter) |
1 |
3823 |
|
2 |
6119 |
|
Test Session (60 min.) |
Performance (MB/s) |
Screenshot (IOmeter) |
1 |
3849 |
|
2 |
9905 |
6. Test conclusions
a. HPT RAID0 (2 Drives): The critical value of TurboWrite buffer is about 221GB.
- Less than or equal to 221GB: normal Sequential write performance. A RAID0 can reach 10GB/s.
- Greater than 221GB: Sequential performance will be reduced to about 3800MB/s
b. TubroWrite performance recovery:
RAID0: By waiting 60min to refresh the TurboWrite area, transfer performance will be restored to 9.9G.