Objective

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.

Default maximum number of write and read requests per second on a bucket

• PUT: 300 requests per second
• GET: 900 requests per second

It is important to note that these maximum values are "soft limits" 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. Indeed, a gradual ramp-up of requests allows you to maximize performance and capitalize on the native sharding of the infrastructure. In other words, limitations can be overcome through a good distribution of the names of the prefixes/object keys and reach multiple thousands of requests per second both in read and write.

Discover how to maximize your performance with this guide.

Service default quotas and limitations

Bucket and object name assignment

• Must be between 3 and 63 characters long.
• Must begin and end with lower case 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 (192.168.1.1).

Features availability

Read our guide on Object Storage - Compatibility.

Go further

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.

Join our community of users.