Content caching best practices for Apple devices
Content caching is primarily affected by two main factors: connectivity and hardware configurations.
You get the best performance from your content cache by connecting it to your network using Gigabit Ethernet. The content cache can serve hundreds of clients concurrently, which can saturate a Gigabit Ethernet port. Therefore, in most small to medium scale deployments, the performance bottleneck is usually the bandwidth of your local network.
To determine if your Mac is the performance bottleneck when a large number of clients are accessing the content cache simultaneously, check the processor usage for the AssetCache process in Activity Monitor (open Activity Monitor, choose View > All Processes, then click CPU). If the processor usage is constantly at or near the maximum, you may want to add additional content caches to distribute the requests across multiple computers.
Also, if your Mac is in an environment where clients download large amounts of a wide variety of content, be sure to set the cache size limit high enough. This prevents the content cache from deleting cached data frequently, which may necessitate downloading the same content multiple times, thereby using more Internet bandwidth.
The following are best practices for content caching. Whenever possible, you should follow these recommendations:
Allow all Apple push notifications.
Don’t use manual proxy settings.
Don’t proxy client requests to content caches.
Bypass proxy authentication for content caches.
Specify a TCP port for caching.
Manage inter-site caching traffic.
Block rogue cache registration.