Typo fixed: Q1T1 R4K writes are 382MB/s, not 882MB/s in my previous post's linked pic.
Yes, so much faster that it's exceeding the PCIe slot speeds by several times
I'm sure there's absolutely no problem with your benchmarks at all
You have an Optane right? Run a benchmark yourself. See for yourself if large Writes are around 12X faster.
That is NOT MY benchmark: It's a pic pulled off the net.
Now:
PCIe3: X2 = 1 969MB/s and X4 = 3 938MB/s
PCIe4: X2 = 3 938MB/s and X4 = 7 877MB/s
https://en.wikipedia.org/wiki/PCI_Express
So even with the typo; An X1 PCI3 slot can do more than "882MB/s".
Now we aren't allowed to call ignorant hars-ols hars-ols here, so I suggest you creep back in under your rock, in shame..! and take some study material with you this time!
One thing to consider before enabling write caching on USB devices is once the handoff to the cache is complete you still need to wait for the data to finish copying before removing the device. Because the data has been handed off to the cache you likely loose the ability to know when the transfer is really complete making device removal at the wrong time risky to the data you wanted on the device. You can use the "safe remove" icon in windows but sometimes that gets hung up from something else accessing your device. When that happens it's very inconvenient when you just need to unplug and go without having to worry if everything has been written. If I recall correctly eSATA also has the same problem if you enable caching.
EDIT: I never finished reading before replying, so the paragraph below this does noy count for you. Soz. This does though:
If something is still writing to your drive after the normal time it takes to get "Safe..." be worried.
Run the drive contents past VirusTotal and do a scan. Then Just pull it; put it back and verify. Natrually you need to do copy-paste-delete, NOT cut-paste, but that's just common practice with most IT Admins etc.
Remember that, like an Optane, old thumb drives have no DRAM cache of their own.
The REG settings apply to a small piece of system RAM.
That means that when you right click the drive and choose "Eject" that RAM buffer is flushed to the drive and you will NOT get a "Safe to unplug" until it is in fact safe.
But yes; you CAN NOT just pull the drive like you don't want the box to get pregnant!
Also NB that the write cache and Max Transfer Length app work best on BOT (protocol) drives.
USB WriteCache does work on UASP enabled flash drives IIRC, but
Max Transfer Length has no effect.
Both work well on older SD Cards, but the new Class A2 cards have a RAM cache of their own. (or they should according to the specification)
I have not tested them.
BTW it was I who pointed out the
Max Transfer Length thing to Uwe, who then wrote the app.
Do give both aps a whirl on older USB stuff AND any fixed drive formatted as anything besides NTF(slow)S. ~ +30% or a minute saved per 3mins!
NB that as a rule of thumb, you need to match MTL to your average file size, but keep the NAND chips' Erase Block Size in mind for writes..! (normally 512KB)
