Azure 檔案服務延展性和效能目標Azure Files scalability and performance targets

Azure 檔案服務可提供在雲端中完全受控的檔案共用,可透過業界標準 SMB 通訊協定加以存取。Azure Files offers fully managed file shares in the cloud that are accessible via the industry standard SMB protocol. 本文討論 Azure 檔案服務和 Azure 檔案同步的延展性和效能目標。This article discusses the scalability and performance targets for Azure Files and Azure File Sync.

此處所列的延展性和效能目標是高階的目標,但可能會受到部署中的其他變數影響。The scalability and performance targets listed here are high-end targets, but may be affected by other variables in your deployment. 例如,檔案的輸送量可能也受限於可用的網路頻寬,而不只是裝載 Azure 檔案服務的伺服器。For example, the throughput for a file may also be limited by your available network bandwidth, not just the servers hosting the Azure Files service. 我們強烈建議您測試您的使用模式,以判斷 Azure 檔案服務的延展性和效能是否符合您的需求。We strongly recommend testing your usage pattern to determine whether the scalability and performance of Azure Files meet your requirements. 我們也保證會隨時間提高這些限制。We are also committed to increasing these limits over time. 歡迎您在底下留言或前往 Azure 檔案服務 UserVoice (英文),提供想要我們提高哪些限制的意見反應。Please don't hesitate to give us feedback, either in the comments below or on the Azure Files UserVoice, about which limits you would like to see us increase.

Azure 儲存體帳戶擴展目標Azure storage account scale targets

Azure 檔案共用的父資源是 Azure 儲存體帳戶。The parent resource for an Azure file share is an Azure storage account. 儲存體帳戶代表 Azure 中可供多個儲存體服務 (包括 Azure 檔案服務) 儲存資料的儲存體集區。A storage account represents a pool of storage in Azure that can be used by multiple storage services, including Azure Files, to store data. 將資料儲存在儲存體帳戶的其他服務有 Azure Blob 儲存體、Azure 佇列儲存體和 Azure 資料表儲存體。Other services that store data in storage accounts are Azure Blob storage, Azure Queue storage, and Azure Table storage. 下列目標適用於在儲存體帳戶中儲存資料的所有儲存體服務:The following targets apply all storage services storing data in a storage account:

下表說明 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.

ResourceResource 預設限制Default limit
每個區域中每個訂用帳戶的儲存體帳戶數目,包括標準和進階帳戶Number of storage accounts per region per subscription, including both standard and premium accounts 250250
儲存體帳戶容量上限Maximum storage account capacity 2 PB,適用于美國和歐洲,而所有其他區域的 500 TB (含英國)12 PB for US and Europe, and 500 TB for all other regions (including the UK)1
每個儲存體帳戶的 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, Europe regions) 25 Gbps25 Gbps
每一儲存體帳戶的輸入上限1 (美國和歐洲以外的地區)Maximum ingress1 per storage account (regions other than US and Europe) 如果啟用了 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 capacity limits and higher limits for ingress by request. 若要要求提高帳戶的輸入限制,請連絡 Azure 支援To request an increase in account limits for ingress, contact Azure Support. 如需詳細資訊, 請參閱宣佈較大型、較大規模的儲存體帳戶For more information, see Announcing larger, higher scale storage accounts.

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. 您可以輕鬆地將一般用途 v1 或 Azure Blob 儲存體帳戶升級至一般用途 v2 帳戶, 而不需停機, 也不需要複製資料。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.

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

ResourceResource 預設限制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 檔案共用。General purpose storage account utilization from other storage services affects your Azure file shares in your storage account. 比方說,如果達到 Azure Blob 儲存體的最大儲存體帳戶容量,您將無法在 Azure 檔案共用上建立新檔案,即使您的 Azure 檔案共用低於最大共用大小也一樣。For example, if you reach the maximum storage account capacity with Azure Blob storage, you will not be able to create new files on your Azure file share, even if your Azure file share is below the maximum share size.

Azure 檔案擴展目標Azure Files scale targets

Azure 檔案儲存體需要考慮的限制有三個類別: 儲存體帳戶、共用和檔案。There are three categories of limitations to consider for Azure Files: storage accounts, shares, and files.

例如: 使用 premium 檔案共用, 單一共用可以達到 100000 IOPS, 而單一檔案可相應增加至 5000 IOPS。For example: With premium file shares, a single share can achieve 100,000 IOPS and a single file can scale up to 5,000 IOPS. 因此, 如果您在一個共用中有三個檔案, 則可以從該共用取得的最大 IOPS 為15000。So, if you have three files in one share, the maximum IOPS you can get from that share is 15,000.

標準儲存體帳戶限制Standard storage account limits

如需這些限制, 請參閱Azure 儲存體帳戶調整目標一節。See the Azure storage account scale targets section for these limits.

Premium FileStorage 帳戶限制Premium FileStorage account limits

進階檔案會使用名為唯一的儲存體帳戶FileStoragePremium files use a unique storage account called FileStorage. 此帳戶類型被設計用於具有高 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

重要

儲存體帳戶限制適用于所有共用。Storage account limits apply to all shares. 只有在每個 FileStorage 帳戶只有一個共用時, 相應增加至 FileStorage 帳戶的最大值才可達到上限。Scaling up to the max for FileStorage accounts is only achievable if there is only one share per FileStorage account.

檔案共用和檔案調整目標File share and file scale targets

注意

超過 5 TiB 的標準檔案共用處於預覽狀態, 且有特定限制。Standard file shares larger than 5 TiB are in preview and have certain limitations. 如需限制清單, 以及在這些較大檔案共用大小的預覽上架, 請參閱規劃指南的標準檔案共用一節。For a list of limitations and to onboard to the preview of these larger file share sizes, see the Standard file shares section of the planning guide.

ResourceResource 標準檔案共用Standard file shares Premium 檔案共用Premium file shares
檔案共用大小上限Minimum size of a file share 沒有最小值;隨用隨付No minimum; pay as you go 100 GiB;預100 GiB; provisioned
檔案共用的大小上限Maximum size of a file share 5 TiB (GA)、100 TiB (預覽)5 TiB (GA), 100 TiB (preview) 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 1000 IOPS (GA),10000 IOPS (預覽)1,000 IOPS (GA), 10,000 IOPS (preview) 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/秒(GA),最高 300 MiB/秒(預覽)Up to 60 MiB/sec (GA), up to 300 MiB/sec (preview) 請參閱 premium 檔案共用輸入和輸出值See premium file share ingress and egress values
單一檔案共用的輸出上限Maximum egress for a single file share 請參閱標準檔案共用目標輸送量See standard file share target throughput 最高 6204 MiB/秒Up to 6,204 MiB/s
單一檔案共用的輸入上限Maximum ingress for a single file share 請參閱標準檔案共用目標輸送量See standard file share target throughput 最高 4136 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

其他進階檔案共用層級的限制Additional premium file share level 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

檔案層級的限制File level limits

領域Area 進階檔案Premium file 標準檔案Standard file
大小Size 1 TiB1 TiB 1 TiB1 TiB
每個檔案的最大 IOPSMax IOPS per file 5,0005,000 1,0001,000
並行控制代碼Concurrent handles 2,0002,000 2,0002,000
輸入Ingress 300 MiB/sec300 MiB/sec 請參閱標準檔案處理量值See standard file throughput values
輸出Egress 200 Mib/sec200 Mib/sec 請參閱標準檔案處理量值See standard file throughput values
ThroughputThroughput 請參閱進階檔案輸入/輸出值See premium file ingress/egress values 最高 60 MiB/秒Up to 60 MiB/sec

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:

ResourceResource 目標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 50000000物件50 million objects No
目錄中的檔案系統物件 (目錄和檔案) 數目上限Maximum number of file system objects (directories and files) in a directory 5000000物件5 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 File Sync performance metrics

由於 Azure 檔案同步代理程式在連線到 Azure 檔案共用的 Windows Server 電腦上執行,有效的同步處理效能取決於基礎結構中的許多因素:Windows Server 和基礎結構磁碟設定、伺服器與 Azure 儲存體之間的網路頻寬、檔案大小、總資料集大小和資料集上的活動。Since the Azure File Sync agent runs on a Windows Server machine that connects to the Azure file shares, the effective sync performance depends upon a number of factors in your infrastructure: Windows Server and the underlying disk configuration, network bandwidth between the server and the Azure storage, file size, total dataset size, and the activity on the dataset. 由於 Azure 檔案同步會在檔案層級上運作,因此 Azure 檔案同步解決方案的效能特性應以每秒處理的物件 (檔案和目錄) 數來測量,以獲得較精準的結果。Since Azure File Sync works on the file level, the performance characteristics of an Azure File Sync-based solution is better measured in the number of objects (files and directories) processed per second.

在下列兩個階段中,Azure 檔案同步必須達到高效能:For Azure File Sync, performance is critical in two stages:

  1. 初始一次性佈建:若要讓初始佈建達到最佳效能,請參閱透過 Azure 檔案同步上架以取得最佳部署的詳細資料。Initial one-time provisioning: To optimize performance on initial provisioning, refer to Onboarding with Azure File Sync for the optimal deployment details.
  2. 持續同步:在 Azure 檔案共用中初次植入資料之後,Azure 檔案同步會將多個端點保持在同步狀態。Ongoing sync: After the data is initially seeded in the Azure file shares, Azure File Sync keeps multiple endpoints in sync.

為了協助您規劃每個階段的部署,以下提供在採用某種組態的系統上進行內部測試期間所觀察到的結果To help you plan your deployment for each of the stages, below are the results observed during the internal testing on a system with a config

系統設定System configuration
CPUCPU 具有 64 MiB L3 快取的 64 個虛擬核心64 Virtual Cores with 64 MiB L3 cache
記憶體Memory 128 GB128 GiB
磁碟Disk 具有電池供電式快取記憶體 RAID 10 的 SAS 磁碟SAS disks with RAID 10 with battery backed cache
網路Network 1 Gbps 的網路1 Gbps Network
工作負載Workload 一般用途檔案伺服器General Purpose File Server
初始一次性佈建Initial one-time provisioning
物件數目Number of objects 2500 萬個物件25 million objects
資料集大小Dataset Size ~ 4.7 TiB~4.7 TiB
平均檔案大小Average File Size ~ 200 KiB (最大檔案:100 GiB)~200 KiB (Largest File: 100 GiB)
上傳輸送量Upload Throughput 每秒 20 個物件20 objects per second
命名空間下載輸送量*Namespace Download Throughput* 每秒 400 個物件400 objects per second

*在建立新的伺服器端點時,Azure 檔案同步代理程式不會下載任何檔案內容。*When a new server endpoint is created, the Azure File Sync agent does not download any of the file content. 它會先同步完整命名空間,然後再觸發背景回復以下載檔案;有可能是下載完整檔案,或者,如果已啟用雲端分層處理,則會根據伺服器端點上設定的雲端分層處理原則進行下載。It first syncs the full namespace and then triggers background recall to download the files, either in their entirety or, if cloud tiering is enabled, to the cloud tiering policy set on the server endpoint.

持續同步Ongoing sync
已同步的物件數目Number of objects synced 125,000 個物件 (~1% 變換)125,000 objects (~1% churn)
資料集大小Dataset Size 50 GiB50 GiB
平均檔案大小Average File Size ~500 KiB~500 KiB
上傳輸送量Upload Throughput 每秒 30 個物件30 objects per second
完整下載輸送量*Full Download Throughput* 每秒 60 個物件60 objects per second

*如果雲端分層處理已啟用,您應該會發現效能有所提升,因為只會下載部分檔案資料。*If cloud tiering is enabled, you are likely to observe better performance as only some of the file data is downloaded. 只有在任何端點上的快取檔案資料有所變更時,Azure 檔案同步才會下載這些資料。Azure File Sync only downloads the data of cached files when they are changed on any of the endpoints. 對於任何分層或新建的檔案,代理程式並不會下載檔案資料,而只會將命名空間同步至所有伺服器端點。For any tiered or newly created files, the agent does not download the file data, and instead only syncs the namespace to all the server endpoints. 代理程式也支援在使用者存取分層的檔案時進行檔案的部分下載。The agent also supports partial downloads of tiered files as they are accessed by the user.

注意

上述數字不代表您將實際體驗到的效能。The numbers above are not an indication of the performance that you will experience. 如本節開頭所述,實際效能將取決於多項因素。The actual performance will depend on multiple factors as outlined in the beginning of this section.

以下提供部署的一般指南,有幾件事您應謹記在心:As a general guide for your deployment, you should keep a few things in mind:

  • 物件輸送量的消長大致上會與伺服器上的同步群組數目成正比。The object throughput approximately scales in proportion to the number of sync groups on the server. 在伺服器上將資料分割到多個同步群組時,會產生較佳的輸送量,但仍受限於伺服器和網路。Splitting data into multiple sync groups on a server yields better throughput, which is also limited by the server and network.
  • 物件輸送量與每秒 MiB 輸送量成反比。The object throughput is inversely proportional to the MiB per second throughput. 檔案較小時,在每秒處理的物件數方面會呈現較高的輸送量,但每秒的 MiB 輸送量則會降低。For smaller files, you will experience higher throughput in terms of the number of objects processed per second, but lower MiB per second throughput. 相反地,若檔案較大,每秒處理的物件數將會降低,但每秒的 MiB 輸送量則會提高。Conversely, for larger files, you will get fewer objects processed per second, but higher MiB per second throughput. 每秒的 MiB 輸送量會受限於 Azure 檔案擴展目標。The MiB per second throughput is limited by the Azure Files scale targets.

另請參閱See also