We're trying to achieve this:
An external 4TB USB SSD that can sustain >870 MB/s sequential write of 2.5TB, in real-world copy of multi-GB files in Windows10, on Threadripper PCs.
Spit in any direction, and you'll find an NVMe SSD that does >2000MB/s. And we easily get 900-1050MB/s in synthetic tests (benchmark utilities). But the above? Me and 3 other technicians have spent a week hacking at it... to no avail. I didn't think this benchmark would be such a holy grail quest.
Our 3 test systems:
2 x Gigabyte TRX40 Desginare, 3960X Threadripper
1 x Gigabyte TRX40 Aorus Master, 3970X Threadripper
1 x ASRock TRX40 Creator, 3960X Threadripper
64GB of RAM or better
(In 2 different cities, so I doubt it's old burial ground voodo causing it.)
Here's an example.
Reading from an internal 4TB Sabrent M.2 NVMe SSD, USB-C 10Gbps mobo port, to a 10Gb USB-C enclosure
1.9TB dataset, average file size 3.3GB.
You can see:
Part 1: Probably the Windows write cache, since that ran at 1.5GB/s, considerably faster than the USB link speed.
Part 2: ~780MB/s, better than 5Gbps speeds...
Part 3: Dropped to a crappy 260MB/s, 20% / 8 minutes / 380GB into the copy
So far we've tried:
Sometimes we get sustained 600MB/s, sometimes we get these:
As said in the beginning, speed tests aren't of much use:
PS If we could get that performance when copying thousands of 30MB files, that'd be great too. Not sure if that size still counts as "large files, sequential" vs. "high-IOPS", hence it might warrant a separate discussion. And I'm focusing on multi-GB files first.
An external 4TB USB SSD that can sustain >870 MB/s sequential write of 2.5TB, in real-world copy of multi-GB files in Windows10, on Threadripper PCs.
Spit in any direction, and you'll find an NVMe SSD that does >2000MB/s. And we easily get 900-1050MB/s in synthetic tests (benchmark utilities). But the above? Me and 3 other technicians have spent a week hacking at it... to no avail. I didn't think this benchmark would be such a holy grail quest.
Our 3 test systems:
2 x Gigabyte TRX40 Desginare, 3960X Threadripper
1 x Gigabyte TRX40 Aorus Master, 3970X Threadripper
1 x ASRock TRX40 Creator, 3960X Threadripper
64GB of RAM or better
(In 2 different cities, so I doubt it's old burial ground voodo causing it.)
Here's an example.
Reading from an internal 4TB Sabrent M.2 NVMe SSD, USB-C 10Gbps mobo port, to a 10Gb USB-C enclosure
1.9TB dataset, average file size 3.3GB.

You can see:
Part 1: Probably the Windows write cache, since that ran at 1.5GB/s, considerably faster than the USB link speed.
Part 2: ~780MB/s, better than 5Gbps speeds...
Part 3: Dropped to a crappy 260MB/s, 20% / 8 minutes / 380GB into the copy
So far we've tried:
- Sabrent 4TB Rocket NVMe (SB-ROCKET-4TB) (QLC)
- Sabrent 4TB Rocket 4 Plus NVMe 4.0 Gen4 ("R/W 7100/6600MB/s") (TLC)
- PNY XLR8 CS3040 4TB NVMe Gen4x4 SSD (TLC)
- Sabrent 10Gbps USB enclosure
- Orico 10Gbps USB enclosure
- Orico 20Gbps USB enclosure with extra heat-sync and active cooling fan
- Changing the Windows device properties to "High performance", and trying different Write cache settings.
- Reformat as GPT / NTFS
- 64KB, 512KB, and 1024KB block size
Sometimes we get sustained 600MB/s, sometimes we get these:


As said in the beginning, speed tests aren't of much use:

PS If we could get that performance when copying thousands of 30MB files, that'd be great too. Not sure if that size still counts as "large files, sequential" vs. "high-IOPS", hence it might warrant a separate discussion. And I'm focusing on multi-GB files first.