| Info |
|---|
ImportantEnable this feature only with Swarm 15 and later versions; do not enable this feature with Swarm 14 and earlier versions. |
Note
Multipart Write was previously referred to as Parallel Write; the functionality is the same.
Parts of a large object from multiple clients at the same time can be uploaded with Multipart Write. Multipart Write allow allows client applications to split a large file in to into multiple pieces, transfer the pieces concurrently to Swarm, and then request that Swarm combine the separately uploaded parts together as a single object, thereby minimizing the upload time.
Multipart write requires erasure coding (Erasure Coding EC). The health processor (HP) has the ability to can consolidate segments of erasure-coded objects with sub-optimal segment usage, as can happen when performing SCSP or S3 multipart writes of objects using small parts. DataCore recommends configuring clients to use 50MB-100MB 50MB–100MB parts. Set the configuration setting, ec.segmentConsolidationFrequency, to 10 (recommended), which performs all consolidations over 20 HP cycles if consolidation is needed.
| Info |
|---|
TipEvery multipart write must be erasure-coded for upload; however, the HP converts it to a replicated object if the uploaded object does not meet the current policy for EC encoding. Add a lifepoint to that effect to maintain erasure coding for the lifetime of the object. |
Three distinct actions must be performed in this order to upload a large object in parts using multipart write:
Initiate a multipart write.
Upload or copy the parts.
Complete or cancel the procedure.
...