Differences

This shows you the differences between two versions of the page.

--- mstream [2018_02_19 20:58] – clarifying text steven
+++ mstream [2022_03_17 12:20] – dan
@@ Line 1: / Line 1: @@
 # M-Stream™ File Transfer Acceleration
+##### last updated on: March 17, 2022
-Transferring large volumes of data systems can be very difficult. Historically it would take users hours or even days to move very large files. The file would be first downloaded from the source system onto their local desktop (if there’s enough room). Only when that’s successful can an upload to the target server begin and fingers crossed an unreliable network doesn’t derail the transfer.
+Transferring large volumes of data can be very difficult. Historically it would take users hours or even days to move very large files. The file would be first downloaded from the source system onto their local desktop (if there’s enough room). Only when that’s successful can an upload to the target server begin and fingers crossed an unreliable network doesn’t derail the transfer.
 M-Stream™ File Transfer Acceleration, available with the Enterprise File Fabric(tm) platform, allows users to transfer files much more quickly. M-Stream transfers files in parallel streams,  speeding up large file downloads, uploads, and movement between storage tiers.
@@ Line 20: / Line 21: @@
 The setting _M-Stream number of threads_ controls the number of threads that will be used during an M-Stream copy or move operation. For best performance, we recommend one thread per CPU core. The default is 2 and the maximum number of threads that can be created is 10.
+<WRAP center round info 100%>
+Both “M-Stream™ number of threads” and “M-Stream™ upload number of threads” are internally capped at 10.  If you set a larger value, the effective value will be 10.
+</WRAP>
 ## Provider Support