traffic estimation edits

This commit is contained in:
Amy Zhou 2022-09-08 00:25:59 -07:00
parent 8a0ae560b7
commit d46aa5111b
3 changed files with 52 additions and 1 deletions

View File

@ -0,0 +1,2 @@
# Cache node configuration

View File

@ -1,5 +1,18 @@
# Client Routing (CIDR, BGP)
Before serving traffic to your customers, client routing configuration is needed. During the configuration of your cache node in Azure portal, you will be able to route your clients to your cache node.
Microsoft Connected Cache offers two ways for you to route your clients to your cache node. The first method of manual entry involves uploading a comma-separated list of CIDR blocks that represents the clients. The second method of setting BGP (Border Gateway Protocol) is more automatic and dynamic, which is set up by establishing neighborships with other ASNs. All routing methods are set up within Azure portal.
To learn more about BGP, ...
Once client routing and other settings are configured, your cache node will be able to download content and serve traffic to your customers.
At this time, only IPv4 addresses are supported. IPv6 addresses are not supported.
### CIDR blocks
CIDR blocks are comprised of IP prefixes (groups of IP addresses) that represent your customer base. You can manually upload a list of your CIDR blocks in Azure portal.
### BGP routing
BGP (Border Gateway Protocol) routing is another method offered for client routing. BGP dynamically retrieves CIDR ranges by exchanging information with routers to understand reachable networks. For an automatic method of routing traffic, you can choose to configure BGP routing in Azure portal.

View File

@ -0,0 +1,36 @@
# Traffic Estimation
During the sign up process, Microsoft will provide you with a traffic estimation based on your ASN(s). We make estimations based on our predictions on historical data about Microsoft content download volume. We will use these estimations to recommend the right hardware for you to deploy your cache node on. You can view these recommendations within the Azure portal.
Note that we make these estimations based on the Microsoft content types that Microsoft Connected Cache serves. To learn more about the types of content that are supported, see [Delivery Optimization and Microsoft Connected Cache content endpoints]().
## Cache performance
To make sure you are maximizing the performance of your cache node, please note the following:
### Drive performance
The maximum number of disks supported is 9. When configuring your drives, we recommend SSD drives as cache read speed of SSD is superior to HDD. In addition, using multiple disks is recommended to improve cache performance.
RAID disk configurations are discouraged as cache performance will be impacted. If using RAID disk configurations, ensure striping.
### NIC requirements
- Multiple NICs on a single MCC instance are supported using a _link aggregated_ configuration.
- 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
### Sizing recommendations
The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice. The following recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC.
| Component | Minimum | Recommended |
| -- | --- | --- |
| OS | Ubuntu 20.04 LTS VM or physical server | Ubuntu 20.04 LTS VM or physical server (preferred) |
| NIC | 10 Gbps| at least 10 Gbps |
| Disk | SSD <br>1 drive <br>2 TB each |SSD <br>2-4 drives <br>at least 2 TB each |
| Memory | 8 GB | 32 GB or greater |
| Cores | 4 | 8 or more |
### Virtual Machines
If you are using a virtual machine as your server, please refer to [VM performance](mcc-isp-vm-performance.md) for tips on how to improve your VM performance.