Object Storage - Limites técnicos (EN)

Bases de conhecimento

KB0047376

Object Storage - Limites técnicos (EN)


Icons/System/eye-open Created with Sketch. 380 visualizações 18.02.2026 Cloud / Object Storage S3

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.

Bucket limitations

Maximum number of buckets per project

Maximum number of objects in a bucket

Unlimited

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).

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 virtual hosting of buckets don't work for buckets with dots in their names.

Object limitations

Maximum size per object / mpu / part

Via a single PUT

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

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 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

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.

Join our community of users.

Artigos relacionados