| title | titleSuffix | description | ms.date | ms.subservice | ms.service | ms.topic | author | ms.author | manager | ms.localizationpriority | ms.reviewer | ms.collection |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
CMG performance and scale |
Configuration Manager |
Plan how the design the cloud management gateway (CMG) for the best performance at the appropriate scale. |
04/08/2022 |
client-mgt |
configuration-manager |
conceptual |
BalaDelli |
baladell |
apoorvseth |
medium |
mstewart,aaroncz |
tier3 |
Applies to: Configuration Manager (current branch)
The supported scale and performance of the cloud management gateway (CMG) is based on the number of devices that you expect to simultaneously connect to the service. Use the information in this article to determine how many of the following components you need in your environment for the best performance at the appropriate scale:
- CMG cloud service
- Virtual machine instances for each CMG
- CMG connection point site system on your internal network
Note
Sizing guidance for management points and software update points doesn't change whether they service on-premises or internet-based clients. For more information, see Size and scale numbers.
[!INCLUDE Size and scale for cloud management gateway]
[!INCLUDE Size and scale for cloud management gateway connection point]
The following recommendations can help you improve CMG performance:
-
The connection between the Configuration Manager client and the CMG isn't region-aware. Client communication is largely unaffected by latency and geographic separation. It's generally not necessary to deploy multiple CMG for the purposes of geo-proximity. Deploy the CMG at the top-level site in your hierarchy. To increase scale, add VM instances.
-
For high availability of the service, create a CMG with at least two VM instances and two CMG connection points per site.
-
Scale the CMG to support more clients by adding more VM instances. The Azure load balancer controls client connections to the service.
-
Create more CMG connection points to distribute the load among them. The CMG distributes the traffic to its connecting CMG connection points in a round-robin fashion.
Note
The CMG connection point creates a TCP connection to the management point for each client. While Configuration Manager has no hard limit on the number of clients for a CMG connection point, Windows Server has a default maximum TCP dynamic port range of 16,384. If a Configuration Manager site manages more than 16,384 clients with a single CMG connection point, add another site system or increase the Windows Server limit. All clients maintain a channel for client notifications, which holds a port open on the CMG connection point. For more information on how to increase this limit, see Microsoft Support article 929851.
As with any distribution point design, consider the following factors for a content-enabled CMG:
- Number of concurrent client connections
- The size of the content that clients download
- The length of time allowed to meet your business requirements
Depending upon your design, if clients have the option of more than one CMG for any given content, then they naturally randomize across those cloud sources. If you only distribute a certain piece of content to a single CMG, and a large number of clients try to download this content at the same time, it puts higher load on that single CMG. Adding another CMG includes a separate Azure storage service. For more information on how the client communicates with the CMG components and downloads content, see Data flow.
Note
The Azure storage service supports 500 requests per second for a single file. Performance testing of a single cloud-based content source supported distribution of a single 100-MB file to 50,000 clients in 24 hours.
Next, understand the costs associated with operating an Azure service for the CMG:
[!div class="nextstepaction"] Cost of CMG