Skip to main content
Load object
Last update:

Load object

You can load objects into a container in two ways:

  • simple upload is available through the dashboard and API. It can be used for files up to 100 MB in size. We do not recommend using Cyrillic characters in object names;
  • segmented-upload is only possible through the Swift API and S3 API. It is recommended to use it for files larger than 100 MB. We do not recommend using Cyrillic characters in object names.

You can load any number of objects into a container, as long as container limits are not set.

Simple download epub⁠

If the name of the object being loaded matches the name of the object in the container, the object will be overwritten.

  1. In Control Panel, go to Object Storage → Containers.
  2. Open the container page → Objects tab.
  3. Select the objects to load.

Segmented download epub⁠

Segmented download is the downloading of objects in parts (segments), which is recommended for files larger than 100 MB. Segmented Upload is only possible via Swift API (SLO/DLO technology) and S3 API (Multipart Upload technology).

It can be used to:

  • load large objects with smaller segments;
  • increase the speed of object loading with the help of parallel queries;
  • in case of connection failures, do not reload the object, but repeat loading of only the necessary segments.

When loading objects via the API, consider the quotas and limits of the storage. Also consider delete segmented objects.

Download the object⁠

You can load an object via segmented loading via S3 API or Swift API methods. The segmented boot process depends on the API and utility used. Some API utilities (Rclone, Cyberduck) support segmented loading and automatically enable it for objects larger than a certain size. In other cases, it must be initialized manually.

When a segmented object is loaded into the main container (<container_name>), a service container is created to hold the object segments:

  • When loading objects via the S3 API, the container is created automatically and is called <container_name>_s3multipartuploads.
  • When loading objects via the Swift API, the container is created using an API or SDK utility and is called <container_name>_segments or <container_name>.file-segments

In the main container (<container_name>), instead of an object, a manifest — a file with a description of segments and the path to them — is loaded. When you download the manifest file, the segments are automatically substituted into the object.

Download speed⁠

The speed of loading objects into containers is affected:

  • channel capacity;
  • connection mode;
  • download manager programs used;
  • the distance between the storage servers and you;
  • host load.

Charging⁠

For any upload method, billed storage capacity, number of API requests, and outbound traffic.

  • at simple upload the storage capacity of an entire object is charged;
  • with segmented-upload, the object is stored in segments, so only segments are actually charged. The manifest file occupies a minimal amount of space (a few KB), so the cost of storing an object with segments is almost the same as the cost of storing an entire object.