@directory_opus Directory Opus seems to be limited to 1GBit / sec transfers even across 10GbE connections. Intended?
Using RAMDisks we've tested the Opus file copy code at speeds over 2 GB/s (gigabytes, not bits). So if the OS, drivers and hardware are buffering data correctly, there should be no bottleneck. Unfortunately, the OS, drivers and hardware are not always that good, or only tuned...
-
-
...to the exact way Explorer (or other things using CopyFileEx) copies data and go much slower when anything else does. As I said, you can play with buffer sizes to get speed increases in a lot of cases, if it isn't going as fast as it should, and we'll be making Opus use...
-
...CopyFileEx in the future (in situations where it is possible to use it; you can't do things like copy to or from an archive using that API, and you'll probably find Explorer has similar bottlenecks there on your hardware, as well as most other software if you measure them).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.