Azure 儲存體延展性和效能目標儲存體帳戶Azure Storage scalability and performance targets for storage accounts

本文會詳細說明 Azure 儲存體帳戶的延展性和效能目標。This article details the scalability and performance targets for Azure storage accounts. 列於此處的延展性和效能目標都是高階目標,但仍可達成。The scalability and performance targets listed here are high-end targets, but are achievable. 在所有情況下,您的儲存體帳戶所達到的要求率和頻寬取決於已儲存物件的大小、使用的存取模式、應用程式執行的工作負載類型。In all cases, the request rate and bandwidth achieved by your storage account depends upon the size of objects stored, the access patterns utilized, and the type of workload your application performs.

請務必測試您的服務,以判斷效能是否達到您的要求。Be sure to test your service to determine whether its performance meets your requirements. 如果可能,請避免流量率突增,確保流量在不同分割之間妥善分散。If possible, avoid sudden spikes in the rate of traffic and ensure that traffic is well-distributed across partitions.

當您的應用程式達到分割區可處理的工作負載限制時,Azure 儲存體會開始傳回錯誤碼 503 (伺服器忙碌) 或錯誤碼 500 (作業逾時) 回應。When your application reaches the limit of what a partition can handle for your workload, Azure Storage begins to return error code 503 (Server Busy) or error code 500 (Operation Timeout) responses. 如果發生 503 錯誤,請考慮將您的應用程式修改為針對重試使用指數輪詢原則。If 503 errors are occurring, consider modifying your application to use an exponential backoff policy for retries. 指數輪詢讓分割的負載減少,也能減輕該分割流量的尖峰。The exponential backoff allows the load on the partition to decrease, and to ease out spikes in traffic to that partition.

儲存體帳戶的規模限制Storage account scale limits

下表說明 Azure 的一般用途 v1,v2 和 Blob 儲存體帳戶的預設限制。The following table describes default limits for Azure general-purpose v1, v2, and Blob storage accounts. 輸入限制是指所有資料傳送至儲存體帳戶的要求。The ingress limit refers to all data from requests that are sent to a storage account. 輸出限制是指所有資料從儲存體帳戶中所收到的回應。The egress limit refers to all data from responses that are received from a storage account.

資源Resource 預設限制Default limit
每個區域中每個訂用帳戶的儲存體帳戶數目,包括標準和進階帳戶Number of storage accounts per region per subscription, including both standard and premium accounts 250250
最大的儲存體帳戶容量Maximum storage account capacity 2 適用於美國和歐洲地區,其他所有區域,其中包括英國的 500 TB 的 PB2 PB for US and Europe, 500 TB for all other regions, which includes the UK
Blob 容器、 blob、 檔案共用、 資料表、 佇列、 實體或訊息,每個儲存體帳戶的最大數目Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 沒有限制No limit
每一儲存體帳戶的要求率上限1Maximum request rate1 per storage account 每秒 20,000 個要求20,000 requests per second
最大輸入1每個儲存體帳戶 (美國地區)Maximum ingress1 per storage account (US regions) 如果啟用 RA-GRS/GRS,則為 10 Gbps,LRS/ZRS 為 20 Gbps210 Gbps if RA-GRS/GRS is enabled, 20 Gbps for LRS/ZRS2
最大輸入1每個儲存體帳戶 (非美國地區)Maximum ingress1 per storage account (non-US regions) 如果啟用 RA-GRS/GRS,則 5 Gbps,LRS/ZRS 為 10 Gbps25 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS/ZRS2
一般用途 v2 和 Blob 儲存體帳戶 (所有區域) 的最大輸出Maximum egress for general-purpose v2 and Blob storage accounts (all regions) 50 Gbps50 Gbps
針對一般用途 v1 儲存體帳戶 (美國地區) 的最大輸出Maximum egress for general-purpose v1 storage accounts (US regions) 如果啟用 RA-GRS/GRS,則為 20 Gbps,LRS/ZRS 為 30 Gbps220 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS2
針對一般用途 v1 儲存體帳戶 (非美國地區) 的最大輸出Maximum egress for general-purpose v1 storage accounts (non-US regions) 如果啟用 RA-GRS/GRS,則為 10 Gbps,LRS/ZRS 為 15 Gbps210 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS2

1azure 標準儲存體帳戶支援的輸入要求,以較高的限制。1Azure Standard Storage accounts support higher limits for ingress by request. 若要要求提高帳戶的輸入限制,請連絡 Azure 支援To request an increase in account limits for ingress, contact Azure Support.

2 Azure 儲存體複寫選項包括:2 Azure Storage replication options include:

  • RA-GRS:讀取權限異地備援儲存體。RA-GRS: Read-access geo-redundant storage. 如果已啟用 RA-GRS,次要位置的輸出目標會與主要位置的輸出目標完全相同。If RA-GRS is enabled, egress targets for the secondary location are identical to those for the primary location.
  • GRS:異地備援儲存體。GRS: Geo-redundant storage.
  • ZRS:區域備援儲存體。ZRS: Zone-redundant storage.
  • LRS:本地備援儲存體。LRS: Locally redundant storage.

注意

我們建議您在大部分情況下,使用一般用途 v2 儲存體帳戶。We recommend that you use a general-purpose v2 storage account for most scenarios. 一般用途 v2 帳戶產生任何停機時間,而且不需要複製資料,您可以輕鬆地升級一般用途 v1 或 Azure Blob 儲存體帳戶。You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data.

如需有關 Azure 儲存體帳戶的詳細資訊,請參閱 < 儲存體帳戶概觀For more information on Azure Storage accounts, see Storage account overview.

如果您應用程式的需求超過單一儲存體帳戶的延展性目標,您可以將應用程式建置為使用多個儲存體帳戶。If the needs of your application exceed the scalability targets of a single storage account, you can build your application to use multiple storage accounts. 接著您可以在這些儲存體帳戶之間分割資料物件。You can then partition your data objects across those storage accounts. 如需批量價格的詳細資訊,請參閱Azure 儲存體定價For information on volume pricing, see Azure Storage pricing.

所有儲存體帳戶都能在一般網路拓撲上執行,並支援本文中說明的延展性和效能目標,無論它們在何時建立。All storage accounts run on a flat network topology and support the scalability and performance targets outlined in this article, regardless of when they were created. 如需 Azure 儲存體平面網路架構及延展性的詳細資訊,請參閱 Microsoft Azure 儲存體:具有高度一致性的高可用性雲端儲存體服務 (英文)。For more information on the Azure Storage flat network architecture and on scalability, see Microsoft Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

進階效能儲存體帳戶調整限制Premium performance storage account scale limits

Premium 效能區塊 blob 儲存體Premium performance block blob storage

使用較小,kb 的範圍,物件的應用程式最適合的 premium 效能區塊 blob 儲存體帳戶。A premium performance block blob storage account is optimized for applications that use smaller, kilobyte range, objects. 它很適合用於需要高交易率或一致的低延遲儲存體應用程式。It's ideal for applications that require high transaction rates or consistent low-latency storage. Premium 效能區塊 blob 儲存體被設計來調整您的應用程式。Premium performance block blob storage is designed to scale with your applications. 如果您打算部署需要數十萬的每秒的要求或以 pb 計的儲存體容量的應用程式,請與我們連絡來提交支援要求中的Azure 入口網站If you plan to deploy application(s) that require hundreds of thousands of requests per second or petabytes of storage capacity, please contact us by submitting a support request in the Azure portal.

進階效能 FileStorage (預覽)Premium performance FileStorage (preview)

進階檔案會使用名為唯一的儲存體帳戶FileStorage (預覽)Premium files use a unique storage account called FileStorage (preview). 此帳戶類型被設計用於具有高 IOPS 工作負載,以一致的低延遲高輸送量。This account type is designed for workloads with high IOPS, high throughput with consistent low-latency. 進階檔案儲存體的延展性與佈建的共用大小。Premium file storage scales with the provisioned share size.

領域Area 目標Target
最大可佈建大小Max provisioned size 100 TiB100 TiB
共用Shares 無限Unlimited
IOPSIOPS 100,000100,000
輸入Ingress 4,136 MiB/s4,136 MiB/s
輸出Egress 6,204 MiB/s6,204 MiB/s

對於進階檔案共用中的擴展目標,請參閱 < 進階檔案調整目標一節。For premium file share scale targets, see the Premium files scale targets section.

Premium 效能分頁 blob 儲存體Premium performance page blob storage

進階效能、 一般用途 v1 或 v2 儲存體帳戶有下列延展性目標:Premium performance, general-purpose v1, or v2 storage accounts have the following scalability targets:

總帳戶容量Total account capacity 本地備援儲存體帳戶總頻寬Total bandwidth for a locally redundant storage account
磁碟容量:35 TBDisk capacity: 35 TB
快照容量:10 TBSnapshot capacity: 10 TB
每秒最多 50 GB (輸入 1 + 輸出 2Up to 50 gigabits per second for inbound1 + outbound2

1 傳送至儲存體帳戶的所有資料 (要求)1 All data (requests) that are sent to a storage account

2 從儲存體帳戶接收的所有資料 (回應)2 All data (responses) that are received from a storage account

如果您針對非受控磁碟使用進階效能儲存體帳戶,而且您的應用程式超過單一儲存體帳戶的延展性目標,您可能想要移轉至受控磁碟。If you are using premium performance storage accounts for unmanaged disks and your application exceeds the scalability targets of a single storage account, you might want to migrate to managed disks. 如果您不想要移轉至受控磁碟,請將應用程式建置為使用多個儲存體帳戶。If you don't want to migrate to managed disks, build your application to use multiple storage accounts. 然後將資料分散到那些儲存體帳戶。Then, partition your data across those storage accounts. 例如,如果您想要將 51 TB 的磁碟連結至多個 VM,可將其分散到兩個儲存體帳戶。For example, if you want to attach 51-TB disks across multiple VMs, spread them across two storage accounts. 單一進階儲存體帳戶的限制是 35 TB。35 TB is the limit for a single premium storage account. 請確定單一的進階效能儲存體帳戶永遠不會有超過 35 TB 的佈建磁碟。Make sure that a single premium performance storage account never has more than 35 TB of provisioned disks.

儲存體資源提供者縮放限制Storage resource provider scale limits

只有在您使用 Azure 儲存體使用 Azure Resource Manager 執行管理作業時,才會適用下列限制。The following limits apply only when you perform management operations by using Azure Resource Manager with Azure Storage.

資源Resource 預設限制Default limit
儲存體帳戶的管理作業 (讀取)Storage account management operations (read) 每 5 分鐘 800800 per 5 minutes
儲存體帳戶管理作業 (寫入)Storage account management operations (write) 每小時 200200 per hour
儲存體帳戶的管理作業 (清單)Storage account management operations (list) 每 5 分鐘 100100 per 5 minutes

Azure Blob 儲存體擴展目標Azure Blob storage scale targets

資源Resource 目標Target
單一 blob 容器的大小上限Maximum size of single blob container 儲存體帳戶容量上限相同Same as maximum storage account capacity
最大數目的區塊中的區塊 blob 或附加 blobMaximum number of blocks in a block blob or append blob 50,000 個區塊50,000 blocks
中的區塊 blob 的區塊大小上限Maximum size of a block in a block blob 100 MiB100 MiB
區塊 blob 的大小上限Maximum size of a block blob 50,000 x 100 MiB (約為 4.75 TiB)50,000 X 100 MiB (approximately 4.75 TiB)
附加 blob 中的區塊大小上限Maximum size of a block in an append blob 4 MiB4 MiB
附加 blob 的大小上限Maximum size of an append blob 50,000 x 4 MiB (約為 195 GiB)50,000 x 4 MiB (approximately 195 GiB)
分頁 blob 的大小上限Maximum size of a page blob 8 TiB8 TiB
每個 blob 容器的預存的存取原則的最大數目Maximum number of stored access policies per blob container 55
單一 Blob 的目標輸送量Target throughput for single blob 儲存體帳戶輸入/輸出限制到1Up to storage account ingress/egress limits1

1單一物件輸送量取決於許多因素,包括但不是限於: 並行存取、 要求大小、 效能層級、 上傳來源和目的地,以下載的速度。1 Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. 若要善用高輸送量的區塊 blob效能增強功能,使用 Put Blob 或 Put Block 要求的大小 > 4 MiB (> 256 KiB premium 效能區塊 blob 儲存體或 Data Lake 儲存體 Gen2)。To take advantage of high-throughput block blob performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 KiB for premium-performance block blob storage or for Data Lake Storage Gen2).

Azure 檔案擴展目標Azure Files scale targets

如需 Azure 檔案服務和 Azure 檔案同步的擴展目標與效能目標的詳細資訊,請參閱 Azure 檔案服務延展性和效能目標For more information on the scale and performance targets for Azure Files and Azure File Sync, see Azure Files scalability and performance targets.

重要

儲存體帳戶限制套用到所有的共用。Storage account limits apply to all shares. 最多調整儲存體帳戶的最大值才可達成,如果沒有每個儲存體帳戶只能有一個共用。Scaling up to the max for storage accounts is only achievable if there is only one share per storage account.

資源Resource 標準檔案共用Standard file shares 進階檔案共用 (預覽)Premium file shares (preview)
檔案共用大小上限Minimum size of a file share 沒有最小值;預付No minimum; pay as you go 100 giB;佈建100 GiB; provisioned
檔案共用的大小上限Maximum size of a file share 5 TiB5 TiB 100 TiB100 TiB
檔案共用中的檔案大小上限Maximum size of a file in a file share 1 TiB1 TiB 1 TiB1 TiB
檔案共用中檔案的最大數目Maximum number of files in a file share 沒有限制No limit 沒有限制No limit
每個共用最大 IOPSMaximum IOPS per share 1,000 IOPS1,000 IOPS 100,000 IOPS100,000 IOPS
每個檔案的預存的存取原則的最大數目的共用Maximum number of stored access policies per file share 55 55
單一檔案共用的目標輸送量Target throughput for a single file share 最高 60 MiB/秒Up to 60 MiB/sec 請參閱進階檔案共用的輸入和輸出值See premium file share ingress and egress values
單一檔案共用的最大輸出Maximum egress for a single file share 請參閱標準檔案共用的目標輸送量See standard file share target throughput 最多 6,204 MiB/秒Up to 6,204 MiB/s
單一檔案共用的最大輸入Maximum ingress for a single file share 請參閱標準檔案共用的目標輸送量See standard file share target throughput 最多 4,136 MiB/秒Up to 4,136 MiB/s
每個檔案的開啟控制代碼數目上限Maximum open handles per file 2,000 個開啟控制代碼2,000 open handles 2,000 個開啟控制代碼2,000 open handles
共用快照集的數目上限Maximum number of share snapshots 200 個共用快照集200 share snapshots 200 個共用快照集200 share snapshots
物件 (目錄和檔案) 名稱長度上限Maximum object (directories and files) name length 2048 個字元2,048 characters 2048 個字元2,048 characters
最大路徑名稱元件 (在路徑 \A\B\C\D 中,每個字母都是元件)Maximum pathname component (in the path \A\B\C\D, each letter is a component) 255 個字元255 characters 255 個字元255 characters

進階檔案調整目標Premium files scale targets

有三種類別的限制時應考量的進階檔案: 儲存體帳戶、 共用和檔案。There are three categories of limitations to consider for premium files: storage accounts, shares, and files.

例如: 單一共用可達到 100,000 IOPS 和單一檔案可以調整最多 5,000 個 IOPS。For example: A single share can achieve 100,000 IOPS and a single file can scale up to 5,000 IOPS. 因此,比方說,如果您有一個共用中的三個檔案,您可以從共用取得的最大 IOPs 是 15000。So, for example, if you have three files in one share, the max IOPs you can get from that share is 15,000.

進階檔案共用限制Premium file share limits

其他進階檔案共用限制Additional premium file share limits

領域Area 目標Target
最小的大小增加/減少Minimum size increase/decrease 1 GiB1 GiB
基準 IOPSBaseline IOPS 每 GiB,最多 100,000 個 1 IOPS1 IOPS per GiB up to 100,000
負載平衡的 IOPSIOPS bursting 3 個 x IOPS 每 GiB,最多 100,000 個3x IOPS per GiB up to 100,000
輸出速率Egress rate 60 MiB/秒 + $0.06 * 佈建 GiB60 MiB/s + 0.06 * provisioned GiB
輸入速率Ingress rate 40 MiB/秒 + 0.04 * 佈建 GiB40 MiB/s + 0.04 * provisioned GiB
快照集的最大數目Maximum number of snapshots 200200

進階檔案限制Premium file limits

領域Area 目標Target
大小Size 1 TiB1 TiB
每個檔案的最大 IOPSMax IOPS per file 5,0005,000
並行控制代碼Concurrent handles 2,0002,000

Azure 檔案同步擴展目標Azure File Sync scale targets

Azure 檔案同步的設計目標是無限制的使用方式,但無限制的使用方式不一定行得通。Azure File Sync has been designed with the goal of limitless usage, but limitless usage is not always possible. 下表指出 Microsoft 的測試界限,也指出哪些目標是固定限制:The following table indicates the boundaries of Microsoft's testing and also indicates which targets are hard limits:

資源Resource 目標Target 固定限制Hard limit
每個區域的儲存體同步服務數目Storage Sync Services per region 20 的儲存體同步服務20 Storage Sync Services Yes
每個儲存體同步服務的同步群組Sync groups per Storage Sync Service 100 個同步群組100 sync groups Yes
每個儲存體同步服務的已註冊伺服器Registered servers per Storage Sync Service 99 部伺服器99 servers Yes
每個同步群組的雲端端點Cloud endpoints per sync group 1 個雲端端點1 cloud endpoint Yes
每個同步群組的伺服器端點Server endpoints per sync group 50 個伺服器端點50 server endpoints No
每部伺服器的伺服器端點Server endpoints per server 30 個伺服器端點30 server endpoints Yes
每個同步群組的檔案系統物件 (目錄和檔案)File system objects (directories and files) per sync group 2500 萬個物件25 million objects No
目錄中的檔案系統物件 (目錄和檔案) 數目上限Maximum number of file system objects (directories and files) in a directory 1 百萬個物件1 million objects Yes
物件 (目錄和檔案) 安全性描述元大小上限Maximum object (directories and files) security descriptor size 64 KiB64 KiB Yes
檔案大小File size 100 GiB100 GiB No
要分層之檔案的檔案大小下限Minimum file size for a file to be tiered 64 KiB64 KiB Yes
並行同步處理工作階段Concurrent sync sessions V4 代理程式和更新版本:可用系統資源限制而有所不同。V4 agent and later: The limit varies based on available system resources.
V3 代理程式:每個處理器或最多八個作用中的同步處理工作階段,每一部伺服器的兩個使用中的同步處理工作階段。V3 agent: Two active sync sessions per processor or a maximum of eight active sync sessions per server.
Yes

注意

Azure 檔案共用的大小,Azure 檔案同步端點可以相應增加。An Azure File Sync endpoint can scale up to the size of an Azure file share. 如果達到 Azure 檔案共用大小限制時,同步處理將會無法運作。If the Azure file share size limit is reached, sync will not be able to operate.

Azure 佇列儲存體擴展目標Azure Queue storage scale targets

資源Resource 目標Target
單一佇列的大小上限Maximum size of a single queue 500 TiB500 TiB
在佇列中訊息的大小上限Maximum size of a message in a queue 64 KiB64 KiB
每個佇列的預存的存取原則的最大數目Maximum number of stored access policies per queue 55
每一儲存體帳戶的要求率上限Maximum request rate per storage account 每秒,會假設 1 KiB 訊息大小 20,000 則訊息20,000 messages per second, which assumes a 1-KiB message size
單一佇列 (1 KiB 訊息) 的目標輸送量Target throughput for a single queue (1-KiB messages) 每秒最多 2,000 個訊息Up to 2,000 messages per second

Azure 資料表儲存體擴展目標Azure Table storage scale targets

資源Resource 目標Target
單一資料表的大小上限Maximum size of a single table 500 TiB500 TiB
資料表實體的大小上限Maximum size of a table entity 1 MiB1 MiB
資料表實體中屬性的最大數目Maximum number of properties in a table entity 255,其中包含三個系統屬性:PartitionKey、 RowKey 和 Timestamp255, which includes three system properties: PartitionKey, RowKey, and Timestamp
中實體的屬性值的總大小上限Maximum total size of property values in an entity 1 MiB1 MiB
每個資料表的預存的存取原則的最大數目Maximum number of stored access policies per table 55
每一儲存體帳戶的要求率上限Maximum request rate per storage account 20,000 每秒交易數,其中假設 1 KiB 實體大小20,000 transactions per second, which assumes a 1-KiB entity size
單一資料表分割區 (1 KiB 實體) 的目標輸送量Target throughput for a single table partition (1 KiB-entities) 每秒最多 2,000 個實體Up to 2,000 entities per second

請參閱See also