Differences

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

--- multipartuploading [2018_02_06 02:16] – Created steven
+++ multipartuploading [2024_02_09 18:55] – old revision restored (2023_06_22 05:41) steven
@@ Line 1: / Line 1: @@
 # Multipart Uploading (MPU, DLO)
+##### last updated on: March 27, 2022
 Multipart uploading (MPU) refers to the ability to create a single large file or object on a server by uploading it in separate segments. Multipart uploading is supported by many object storage platforms and is preferred, and even required, when creating objects over a certain size.
@@ Line 17: / Line 17: @@
 Multipart uploading will only be used if enabled for a storage provider. This setting can be enabled or disabled through the Dashboard Provider Settings:
-{{ :multipartuploading:provider-options-mpu.png |}}
+{{ :multipartuploading:provider-options-mpu.png?400 |}}
 The Multipart upload size setting is optional. If blank the appliance "Default multipart upload size" is used.
+<WRAP center round info 100%>
+If you set an explicit MPU size for a provider then that size will always be used with that provider.  If you don’t set an explicit MPU size for a provider and you are using M-Stream then the MPU size that is used may be different than the appliance default MPU size.
+</WRAP>
 OpenStack Swift providers allow support multipart uploads through Dynamic Large Objects. These can also be enabled and a minimum file size set through the Provider Settings:
-{{ :multipartuploading:provider-options-dlo.png |}}
+{{ :multipartuploading:provider-options-dlo.png?400 |}}