View content caching logs and statistics
View content caching logs
Content caching logs messages to the subsystem com.apple.AssetCache. You can use the
log command in Terminal to view the logs, or you can use the Console app to view the logs.
View the logs in Terminal: Open the Terminal app, then enter a
logcommand. For example:
$ log show --predicate 'subsystem == "com.apple.AssetCache"'
View the logs in Console: Open the Console app, type s:com.apple.AssetCache in the search field, then press return.
You can increase the amount of information logged by the content cache. For more information, see the Verbose key in Configure advanced content caching settings.
For more information about using the
log command, see the log(1) man page.
View content caching statistics
You can use Activity Monitor to view statistics about content caching, such as the amount of data uploaded to and served from the content cache. Activity Monitor displays statistics for the last hour, last 24 hours, last 7 days, and last 30 days.
Open Activity Monitor, then click Cache.
The Cache option is available in Activity Monitor only after content caching has been turned on once. If you don’t see the Cache option, try restarting Activity Monitor.
For a description of the available statistics, see View content cache activity in Activity Monitor help.
You can use the statistics to evaluate the performance of a content cache. For example:
Determine whether content caching is working: The content cache is working if the values in the Data Served row are greater than zero.
Determine whether content caching is helping: The closer the Data Served From Cache values are to the Data Served values, the more content caching is helping.
Determine whether the content cache has enough space: If the values in the Maximum Cache Pressure row are higher than 50%, the content cache needs more space. You can assign more space to it, move the cache to a larger volume, or do both. For information about changing the cache size, see Set the cache size. For information about moving the cache, see Manage content caching from the command line.