Differences

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

--- multipartuploading [2018_02_06 02:17] – made last 2 images smaller steven
+++ multipartuploading [2024_02_28 01:03] (current) – external edit 127.0.0.1
@@ 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.
-The Enterprise File Fabric can use multipart uploading for object storage providers that support the MPU (S3 Compatible) or DLO (OpenStack Swift). It can be enabled on a per provider basis.
+Access Anywhere can use multipart uploading for object storage providers that support the MPU (S3 Compatible) or DLO (OpenStack Swift). It can be enabled on a per provider basis.
 ##Appliance Configuration
@@ Line 20: / Line 20: @@
 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: