Object Storage Service:Limits and performance metrics

Bandwidth

The following table lists the maximum bandwidth for a single Alibaba Cloud account in each region.

If the threshold is reached, requests are throttled. When a request is throttled, the response header contains x-oss-qos-delay-time: number. In this header, number indicates the throttling duration in milliseconds. For upload requests, the header returns the exact throttling duration. For download requests, the header returns an estimated throttling duration based on the throttling level and file size.

Requests from OSS background tasks, such as lifecycle rules, cross-region replication, same-region replication, and last access time updates, do not consume your account's QPS and bandwidth quotas. Only read, write, and delete operations initiated using temporary credentials from AssumeRole are counted. For example, the automatic deletion of expired objects by a lifecycle policy does not use your account's QPS quota for delete operations. The cross-region replication feature has a separate QPS quota that is independent of your account's QPS quota.

Queries per second (QPS)

A single Alibaba Cloud account supports up to 10,000 queries per second (QPS). The actual maximum QPS varies based on the read and write mode:

If you upload many files using names with sequential prefixes, such as timestamps or alphabetical characters, the indexes for these files may be concentrated in a specific partition of the bucket. If the request rate is too high, performance may degrade. We recommend that you avoid using sequential prefixes for file names when you upload many files. For more information about how to change sequential prefixes to random prefixes, see OSS performance best practices.

Buckets

• An Alibaba Cloud account can have up to 100 buckets in a single region. If your business requires more buckets, you can submit a request in Quota Center.

• Bucket names must be globally unique within OSS. For more information about naming conventions, see Bucket naming conventions.

• After a bucket is created, you cannot change its name, region, or storage class.

• There is no limit on the capacity of a single bucket.

Objects

• Object size for uploads

  The size of a single object uploaded using simple upload, form upload, or append upload cannot exceed 5 GB.

  The size of a single object uploaded using multipart upload cannot exceed 48.8 TB.

• Renamed file size

  In the OSS console, you can rename only objects that are 1 GB or smaller. To rename objects larger than 1 GB, use an SDK or the ossutil command line tool. For more information, see Rename objects.

• Number of objects for deletion

  You can delete up to 100 objects at a time in the OSS console, or 1,000 objects at a time using an SDK. There is no limit on the number of objects you can delete at a time using the ossutil command line tool or the ossbrowser graphical tool.

  Warning

  Deleted objects cannot be recovered. Proceed with caution.

• Overwriting objects with the same name

  By default, if you upload an object with the same name as an existing object, the existing object is overwritten.

  Warning

  Overwritten objects cannot be recovered. Proceed with caution. To prevent objects from being accidentally overwritten, you can enable versioning for the bucket where the objects are stored. You can also include the x-oss-forbid-overwrite header in the upload request and set its value to true.

Data restoration

Before you can access data in the Archive (if real-time access of Archive objects is not enabled), Cold Archive, or Deep Cold Archive storage classes, you must first restore the data. A higher restoration priority results in a shorter restoration time and higher data retrieval fees. For more information, see Data retrieval fees.

You can still submit restoration requests after the reference quotas for Cold Archive and Deep Cold Archive objects are exceeded. The restore request is queued, and the time required to complete the restore task may be longer than the expected time corresponding to the selected priority.

Domain name binding

• Domain names bound to buckets in regions in the Chinese mainland must have an ICP filing from the MIIT. This is not required for buckets in other regions.

• A domain name can be bound to only one bucket. A bucket can have up to 100 domain names bound to it.

• You can attach an unlimited number of domain names to a single account.

Lifecycle rules

• You can configure up to 1,000 lifecycle rules for a bucket.

• Execution time:

  • After a rule takes effect, lifecycle operations such as object deletion, storage class transition, and expiration of multipart upload parts are typically completed within 24 hours for up to 1 billion objects in the China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), and Singapore regions. In other regions, these operations are typically completed within 24 hours for up to 100 million objects.

  • Execution may take longer than 24 hours, and in some cases several days or weeks, if there are many objects to scan, many objects to which the lifecycle rule applies, many tags, many versions for a single object, or a high volume of new objects being written while the lifecycle task is running.

    Note

    If versioning is enabled for the bucket, an operation on each version of an object is counted as a separate operation.

Back-to-origin rules

• You can configure up to 20 back-to-origin rules for a bucket.

• For mirroring-based back-to-origin, the default QPS is 2,000 and the default bandwidth is 2 Gbit/s in regions in the Chinese mainland and the China (Hong Kong) region. In other regions, the default QPS is 1,000 and the default bandwidth is 1 Gbit/s.

Image processing

• Image limits

  • Source images

    • Supported formats are JPG, PNG, BMP, GIF, WebP, TIFF, HEIC, and AVIF.

    • The source image cannot exceed 20 MB.

    • For rotation, the height or width of the source image cannot exceed 4,096 pixels. For other operations, the height or width cannot exceed 30,000 pixels, and the total number of pixels cannot exceed 250 million.

      The total number of pixels for a dynamic image, such as a GIF, is calculated as Width × Height × Number of frames. The total number of pixels for a static image, such as a PNG, is calculated as Width × Height.

  • Scaled image

    Neither the width nor the height can exceed 16,384 pixels, and the total number of pixels cannot exceed 16,777,216.

• Style limits

  You can create up to 50 styles for each bucket.

• Processing capacity limits

  • Image processing throughput per second (by source image size)

    • China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), and China (Shenzhen): 20 MB/s.

    • Other regions: 2 MB/s.

  • Queries per second (QPS)

    • China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), and China (Shenzhen): 50.

    • Other regions: 5.

Resource plans

• Region-specific resource plans can offset fees only in the region for which they are purchased.

• You cannot change the region of a purchased resource plan.

• You cannot use multiple storage plans concurrently. However, you can upgrade your purchased storage plan.

• You can use multiple transfer acceleration plans and back-to-origin traffic plans concurrently. However, these plans cannot be upgraded or renewed.

• You can use and renew multiple outbound data transfer plans concurrently. However, these plans cannot be upgraded.

• Resource plans are currently not available for Request fees, Data processing fees, and cross-region replication traffic fees, which are included in Traffic fees. These fees are charged on a pay-as-you-go basis and do not support subscription.