Contents
By monitoring cache performance, you can make sure that that the farm cache settings are correct and that the caching is running at maximum performance. SharePoint Server 2016 provides three types of caches that help improve the speed at which web pages load in the browser: the BLOB cache, the ASP.NET output cache, and the object cache.
SharePoint Server 2016 collects data in the diagnostic log that you can use to troubleshoot the SharePoint Server 2016 farm environment. The default settings are sufficient for most situations, but depending upon the business needs and lifecycle of the farm, you might want to change these settings.
To review and update the timer jobs, see View timer job status in SharePoint Server 2016. SharePoint Server 2016 includes an integrated health analysis tool that is named SharePoint Health Analyzer that you can use to check for potential configuration, performance, and usage problems.
What are the monitoring settings in SharePoint Server 2016?
SharePoint Server 2016 comes installed with default settings for its monitoring features. However, you might want to change some of these settings to better suit business needs. These settings include diagnostic logging and usage and health data collection. Diagnostic logging collects data about the SharePoint Server 2016 farm environment.
Where is the cache located in SharePoint Server?
This cache helps users when they browse to pages that use these features because the data that they require is stored or retrieved directly from the object cache instead of from the content database. The object cache is stored in the RAM of each web server in the farm. Each web server maintains its own object cache.
You enable the BLOB cache in the Web.config file of the web application to which you want to apply it. The changes that you make to the Web.config file will be applied to all site collections within the web application.
The scripts performs the following tasks: Loads the SharePoint add-in into PowerShell. Stops the SharePoint Timer Service. Deletes the cache (xml) files. Resets the cache by setting the value in the cache.ini file to 1. Starts the SharePoint Timer Service.