Object Storage Service:Limits and performance metrics of OSS

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. The number parameter indicates the duration for which the request is throttled, in milliseconds (ms). For upload requests, the exact throttling duration is returned. For download requests, an estimated throttling duration is returned based on the throttling degree and file size.

Queries per second (QPS)

The total queries per second (QPS) for a single Alibaba Cloud account is 10,000. However, the actual QPS varies based on the read/write mode, as shown in the following table:

When you upload many files, using sequential prefixes in filenames, such as timestamps or alphabetical orders, can cause performance issues. This is because the file indexes might all be stored in a single partition of the bucket. If your request rate is too high in this scenario, performance will decrease. When you upload many files, avoid using sequential prefixes in filenames. For information about how to change sequential prefixes to random prefixes, see OSS performance best practices.

Buckets

• The total number of buckets that can be created by a single Alibaba Cloud account in a region cannot exceed 100. 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 bucket naming conventions, see Bucket naming.

• After a bucket is created, its name, region, and storage class cannot be changed.

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

• Object size for renaming

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

• Number of objects for deletion

  You can delete a maximum of 100 objects at a time in the OSS console, a maximum of 1,000 objects at a time using an SDK, and an unlimited number of objects at a time using the ossutil command line interface or the ossbrowser graphical tool.

  Warning

  Deleted objects cannot be restored. Proceed with caution.

• Overwriting objects with the same name

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

  Warning

  The original object is lost after it is overwritten. Proceed with caution. To prevent objects from being accidentally overwritten, you can enable versioning for the bucket where the objects are stored, or include the x-oss-forbid-overwrite parameter in the header of the upload request and set its value to true.

Data restoration

Before you can access data in the Archive Storage (if real-time access of Archive objects is disabled), Cold Archive, or Deep Cold Archive storage class, you must wait for the data to be restored. The higher the restoration priority, the shorter the restoration time and the higher the 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 that are bound to buckets in regions in the Chinese mainland must have an ICP filing. Domain names that are bound to buckets in other regions do not require an ICP filing.

• A domain name can be bound to only one bucket. A bucket can be bound to a maximum of 100 domain names.

• There is no limit on the number of domain names that can be bound to an account.

Lifecycle rules

• You can configure a maximum of 1,000 lifecycle rules for a bucket.

• Completion time:

  • After a rule takes effect, lifecycle operations, such as object deletion, object storage class conversion, and fragment expiration, are typically completed within 24 hours. In the China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), and Singapore regions, this applies to operations on up to 1 billion objects. In other regions, this applies to operations on up to 100 million objects.

  • The task may take more than 24 hours, or even several days to weeks, to complete in the following cases: many objects are scanned, many objects are processed by lifecycle rules, there are many tags, an object has many historical versions, or many new objects are 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 a maximum of 20 back-to-origin rules for a bucket.

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

Image processing

• Image limits

  • Source image

    • The image format must be JPG, PNG, BMP, GIF, WebP, TIFF, HEIC, or AVIF.

    • The source image cannot exceed 20 MB in size.

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

      For dynamic images, such as GIF images, the number of pixels is calculated as width × height × number of frames. For non-dynamic images, such as PNG images, the number of pixels is calculated as width × height.

  • Resized image

    The width or height cannot exceed 16,384 pixels, and the total number of pixels cannot exceed 16,777,216.

• Style limits

  You can create a maximum of 50 styles for each bucket.

• Processing capacity limits

  • Image processing throughput per second (based on 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 be used only in the regions for which they are purchased.

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

• You cannot purchase multiple storage plans. However, you can upgrade a purchased storage plan.

• You can purchase multiple transfer acceleration plans and back-to-origin traffic plans. However, you cannot upgrade or renew these plans.

• You can purchase and renew multiple outbound data transfer plans. However, you cannot upgrade these plans.

• Request fees, data processing fees, and cross-region replication traffic fees are not covered by resource plans and are billed on a pay-as-you-go basis.