Object Storage: Technical Limitations – Support Guides

This page provides an overview of the technical limitations of the OVHcloud Object Storage offer.

Performance

Maximum bandwidth per connection

1 Gbps/connection.

As OVHcloud Object Storage is a highly distributed system, using parallel requests will help overcome this limitation. Depending on your application and use case, this can be accomplished by simultaneously initiating requests (also called concurrent requests).

Discover how to maximize your performance with this guide.

Maximum number of write requests per second on a bucket

300 (beyond this number, the quality of service is no longer guaranteed).

This maximum value is a soft limit and can be easily overcome by adopting best practices to distribute the I/Os as widely as possible in the object storage cluster, taking advantage of the sharding mechanism.

Discover how to maximize your performance with this guide.

Bucket limitations

Maximum number of containers per project

100 (default)
1,000 (requires manual intervention, please contact the support team)

Maximum number of objects in a bucket

Unlimited

Object limitations

Maximum size per object/mpu/part

Via a single PUT

Maximum 5 GB per object (use a multi-part upload for an object whose size is above 5GB).

Via a multi-part upload (MPU)

The size for a single part must be between 5MB (minimum) and 5GB (maximum)
10000 parts maximum in a mpu

The theoretical maximum size of a single large object uploaded via MPU is thus 48TB.

Project limitations

Maximum number of user accounts per project

1,000

Name assignment

Must be between 3 and 63 characters long.
Must begin and end with lowercase alphanumeric characters (a to z and 0 to 9).
Must be unique within OVHcloud.
May contain the following punctuation marks: . and -.
Must not contain multiple punctuation marks in a row (e.g. .. or -. or .- or --).
Must not look like an IP address (e.g. 192.168.1.1).

NOTE: For best compatibility, we recommend that you avoid using dots (.) in bucket names, except for buckets that are used only for static website hosting. If you include dots in a bucket's name, you can't use virtual-host-style addressing over HTTPS, unless you perform your own certificate validation. This is because the security certificates used for the virtual hosting of buckets don't work for buckets with dots in their names.

Feature availability

See our Object Storage - Compliancy guide.

NOTE: For Local Zones, the number of objects and used space are currently unavailable in the OVHcloud Control Panel.

Go further

For more information and tutorials, please see our other Object Storage support guides or explore the guides for other OVHcloud products and services.