Limits - Object Storage Service - Alibaba Cloud Documentation Center

This topic describes the performance metrics and limits of Object Storage Service (OSS).

The following table describes the performance metrics and limits of OSS.

Item	Description
Bandwidth	OSS has an upper limit on bandwidth per region within an Alibaba Cloud account: China (Hangzhou) and China (Zhangjiakou): Both the total upload bandwidth and the total download bandwidth over private and public networks are 20 Gbit/s for either of the regions. China (Shanghai), China (Shenzhen), and China (Beijing): For each of the regions, the total upload bandwidth over private and public networks is 20 Gbit/s, with the maximum upload bandwidth over the public network limited to 10 Gbit/s. For each of the regions, the total download bandwidth over private and public networks is 100 Gbit/s, with the maximum download bandwidth over the public network limited to 10 Gbit/s. Other regions in the Chinese mainland: Both the total upload bandwidth and the total download bandwidth over private and public networks are 10 Gbit/s for each of the Chinese mainland regions except for China (Hangzhou), China (Zhangjiakou), China (Shanghai), China (Shenzhen), and China (Beijing). Regions outside the Chinese mainland: Both the total upload bandwidth and the total download bandwidth over private and public networks are 5 Gbit/s for each of the regions. If the maximum bandwidth limit is reached, further requests are throttled. Note When a request is throttled, the response to the request contains the `x-oss-qos-delay-time: number` header, in which `number` indicates the duration in milliseconds for which the request is throttled. For a throttled upload request, this header indicates the exact duration of throttling. For a throttled download request, this header indicates a throttling duration estimated based on the extent of throttling and the object size. The bandwidth limits can be increased to meet higher bandwidth requirements for business applications such as big data offline processing. To request an increase of bandwidth limits, contact technical support.
QPS	The total queries per second (QPS) for an Alibaba Cloud account is 10,000. The actual maximum QPS performance varies based on the read and write modes: Sequential read and write: 2,000 If you upload a large number of objects and the names of the objects contain sequential prefixes such as timestamps and letters, multiple object indexes may be stored in a single partition. In this case, if you send a large number of requests to query these objects, latency is increased. We recommend that you do not upload a large number of objects whose names contain sequential prefixes. For more information about how to change sequential prefixes to random prefixes, see OSS performance and scalability best practices. Non-sequential read and write: 10,000 If your business requires a higher QPS, contact technical support.
Bucket	Up to 100 buckets can be created per region within an Alibaba Cloud account. A bucket name must be globally unique in OSS. For more information about bucket naming, see Bucket naming conventions. After a bucket is created, you cannot change its name, region, or storage class. OSS does not limit the capacity of a bucket.
Object	The size of an object that you can upload When you use simple upload, form upload, or append upload to upload an object, the size of the object cannot exceed 5 GB. For more information, see Simple upload, Form upload, and Append upload. When you use multipart upload to upload an object, the size of the object cannot exceed 48.8 TB. For more information, see Multipart upload. The size of an object that you can rename You can rename only objects whose sizes are less than or equal to 1 GB in the OSS console. If you want to rename objects whose sizes exceed 1 GB, we recommend that you use OSS SDKs or ossutil. For more information, see Rename objects. The number of objects that you can delete You can delete up to 100 objects at a time in the OSS console or up to 1,000 objects at a time by using OSS SDKs. You can delete an unlimited number of objects at a time by using ossutil or ossbrowser. Warning Deleted objects cannot be recovered. We recommend that you exercise caution when you delete objects. Overwrites of same-name objects By default, if you upload an object that has the same name as an existing object, the existing object is overwritten. Warning Overwritten objects cannot be recovered. We recommend that you exercise caution when you overwrite objects. To prevent objects from being accidentally overwritten, you can enable versioning for the bucket in which the objects are stored. You can also include the x-oss-forbid-overwrite header in upload requests and set the header to true.
Data restoration	Before you can access Archive (if real-time access of Archive objects is not enabled), Cold Archive, or Deep Cold Archive objects, you must first restore them. The higher the restore priority, the less the restoration time and the higher the data retrieval fee. For more information, see the OSS Billing Details section on the OSS product page. Archive The time required to restore an Archive object is several minutes. Cold Archive The time required to restore a Cold Archive object varies based on the restoration priority. Expedited: within 1 hour Standard: 2 to 5 hours Bulk: 5 to 12 hours Note An average of 500 Cold Archive objects can be restored per second per region within an Alibaba Cloud account. The total amount of data retrieved based on the preceding priorities ranges from 100 TB to 120 TB per day. If you want to increase the data retrieval limit, contact technical support. Deep Cold Archive The time required to restore a Deep Cold Archive object varies based on the restoration priority. Expedited: within 12 hours Standard: within 48 hours Note An average of 100 Deep Cold Archive objects can be restored per second per region within an Alibaba Cloud account. The total amount of data retrieved based on the preceding priorities ranges from 10 TB to 15 TB per day. If you want to increase the data retrieval limit, contact technical support.
Domain name mapping	For a domain name that is mapped to a bucket located in a region in the Chinese mainland, you must apply to the Ministry of Industry and Information Technology (MIIT) for an ICP filing. Up to 100 domain names can be mapped to a bucket. However, a domain name can be mapped to only one bucket. OSS does not limit the number of domain-and-bucket mappings within an Alibaba Cloud account.
Lifecycle rules	You can configure up to 1,000 lifecycle rules for a bucket. Completion time For a lifecycle rule that does not contain tags, you can perform up to 1 billion lifecycle-related operations in 24 hours, including object deletion, storage class conversion, and the operation that can be performed on the expired parts. If you want to perform more than 1 billion lifecycle-related operations, the time period that is required to complete the operations may exceed 24 hours. For a lifecycle rule that contains tags, you can perform up to 500 million lifecycle-related operations in 24 hours, including object deletion, storage class conversion, and the operation that can be performed on the expired parts. If you want to perform more than 500 million lifecycle-related operations, the time period that is required to complete the operations may exceed 24 hours. Note If versioning is enabled for the bucket, an operation performed on each version of the objects is recorded as an operation.
Back-to-origin rules	You can configure up to 20 back-to-origin rules for a bucket. In regions in the Chinese mainland and the China (Hong Kong) region, the default QPS limit and the default bandwidth limit for mirroring-based back-to-origin requests are 2,000 and 2 Gbit/s, respectively. In regions outside China, the default QPS limit and the default bandwidth limit for mirroring-based back-to-origin requests are 1,000 and 1 Gbit/s, respectively.
Image processing	Limits on images Source images Only JPG, PNG, BMP, GIF, WebP, TIFF, HEIC, and AVIF images are supported. The size of a source image cannot exceed 20 MB. For the rotate operation, the height or width of a source image cannot exceed 4,096 pixels. For other operations, the width or height of a source image cannot exceed 30,000 pixels, and the total number of pixels of the source image cannot exceed 250 million. The total number of pixels of a dynamic image, such as a GIF image, is calculated by using the following formula: `Width × Height × Number of image frames`. The total number of pixels of a static image, such as a PNG image, is calculated by using the following formula: `Width × Height`. Resized images The width or height of a resized image cannot exceed 16,384 pixels. The total number of pixels of a resized image cannot exceed 16,777,216. Limits on image styles You can create up to 50 image styles for a bucket. If your business requires more than 50 styles, contact technical support. Limits on processing capabilities Per-second processing throughput (by source image) The maximum throughput of image processing is 20 MB/s for China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), and China (Shenzhen). The maximum throughput of image processing for other regions is 2 MB/s. QPS The QPS limit is 50 for China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), and China (Shenzhen). The QPS limit for other regions is 5. Note You may want to go beyond the preceding limits in computationally intensive business applications, such as encoding WebP, AVIF, or HEIF images at a resolution higher than 1080p. To increase the limits, contact technical support.
Storage plans	Resource plans that you purchase for a specific region can be used to offset the fees for resource usage only in the region. You cannot change the region of a purchased resource plan. You can purchase only one storage plan for a given period of time. However, you can upgrade the storage plan that you purchased. For more information about how to upgrade a storage plan, see Overview. You can purchase multiple transfer acceleration plans and back-to-origin traffic plans that have the same validity period to offset your fees. However, these plans cannot be upgraded or renewed. You can purchase multiple outbound traffic plans that have the same validity period to offset your fees. These plans can be renewed but cannot be upgraded. No resource plans are available to offset API operation calling fees, data processing fees, and cross-region replication (CRR) traffic fees. You are charged these fees on a pay-as-you-go basis. For more information, see API operation calling fees, Data processing fees, and Traffic fees.