# Cache Monitoring SharePoint 2013

- Link: https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/
- Published: 2015-05-03T04:35:08+05:30
- Author: Deviprasad Panda

SharePoint 2013 provides three types of caches that help improve the speed at
which web pages load in the browser: the [BLOB ](https://sharepointtechnicalsupport.com/category/blobstorage/)
cache, the ASP.NET output cache, and the object [cache](https://sharepointtechnicalsupport.com/category/cache-2/).

 * The **BLOB cache** is a disk-based cache that stores binary large object files
   that are used by web pages to help the pages load quickly in the browser.
 * The **ASP.NET output cache** stores the rendered output of a page. It also stores
   different versions of the cached page, based on the [permissions ](https://sharepointtechnicalsupport.com/category/permission/)
   of the users who are requesting the page.
 * The **object cache** reduces the traffic between the web server and the [SQL ](https://sharepointtechnicalsupport.com/category/sql/)
   database by storing objects such as lists and libraries, site settings, and page
   layouts in memory on the front-end web server. As a result, the pages that require
   these items can be rendered quickly, increasing the speed with which pages are
   delivered to the client browser.

Monitoring consists of regularly viewing specific performance monitors and making
adjustments in the settings to correct any performance issues. The monitors measure
cache hits, cache misses, cache compactions, and cache flushes. The following list
describes each of these performance monitors.

 * A **cache hit** occurs when the cache receives a request for an object whose 
   data is already stored in the cache. A high number of cache hits indicates good
   performance and a good end-user experience.
 * A **cache miss** occurs when the cache receives a request for an object whose
   data is not already stored in the cache. A high number of cache misses might 
   indicate poor [performance ](https://sharepointtechnicalsupport.com/category/performance/)
   and a slower end-user experience.
 * **Cache compaction** (also known as trimming), happens when a cache becomes full
   and additional requests for non-cached content are received. During compaction,
   the system identifies a subset of the contents in the cache to remove, and removes
   them. Typically these contents are not requested as frequently.
    Compaction can
   consume a significant portion of the server’s resources. This can affect both
   server performance and the end-user experience. Therefore, compaction should 
   be avoided. You can decrease the occurrence of compaction by increasing the size
   of the [cache](https://sharepointtechnicalsupport.com/category/cache-2/). Compaction
   usually happens if the cache size is decreased. Compaction of the object cache
   does not consume as many resources as the compaction of the [BLOB ](https://sharepointtechnicalsupport.com/category/blobstorage/)
   cache.
 * A **cache flush** is when the cache is completely emptied. After the [cache ](https://sharepointtechnicalsupport.com/category/cache-2/)
   is flushed, the cache hit to cache miss ratio will be almost zero. Then, as users
   request content and the cache is filled up, that ratio increases and eventually
   reaches an optimal level. A consistently high number for this counter might indicate
   a problem with the farm, such as constantly changing library metadata schemas.

You can monitor the effectiveness of the cache settings to make sure that the end-
users are getting the best experience possible. Optimum [performance ](https://sharepointtechnicalsupport.com/category/performance/)
occurs when the ratio of [cache ](https://sharepointtechnicalsupport.com/category/cache-2/)
hits to cache misses is high and when compactions and flushes only rarely occur.
If the monitors do not indicate these conditions, you can improve performance by
changing the cache settings.

The following sections provide specific information for monitoring each kind of 
cache.

[Monitoring BLOB cache performance](https://www.blogger.com/null)

You can monitor the effectiveness of the cache settings by using the [performance ](https://sharepointtechnicalsupport.com/category/performance/)
monitors that are listed in the following table.

### SharePoint Publishing Cache counter group

  |  Counter name |  Ideal value or pattern |  Notes |  
 |  Total Number of cache Compactions |  0 |  If this number is continually or frequently high, the cache size is too small for the data being requested. To improve performance, increase the size of the cache. |  
 |  BLOB Cache % full |  >= 90% shows red>= 80% shows yellow

<80% shows green

 |  This can show that the cache size is too small. To improve performance, increase the size of the cache. |  
 |  Publishing cache flushes / second |  0 |  Site owners might be performing actions on the sites that are causing the cache to be flushed. To improve performance during peak-use hours, make sure that site owners only perform these actions during off-peak hours. |  
 |  Publishing cache hit ratio |  Depends on usage pattern. For read-only sites, the ratio should be 1. For read-write sites, the ratio may be lower. |  A low ratio can indicate that unpublished items are being requested, and these cannot be cached. If this is a portal site, the site might be set to require check-out, or many users have items checked out. |

**Note :**

For the BLOB cache, a request is only counted as a cache miss if the user requests
a file whose extension is configured to be cached. For example, if the cache is 
enabled to cache .jpg files only, and the cache gets a request for a .gif file, 
that request is not counted as a cache miss.

[Monitoring ASP.NET output cache performance](https://www.blogger.com/null)

You can monitor the effectiveness of the cache settings by using the performance
monitors that are listed in the following table.

### ASP.NET Applications counter group

  |  Counter name |  Ideal value or pattern |  Notes |  
 |  Cache API trims |  0 |  Increase the amount of memory that is allocated to the ASP.NET output cache. |  
 |  Cache API hit ratio |  Depends on usage pattern. For read-only sites, the ratio should be 1. For read-write sites, the ratio may be lower. |  Potential causes of a low hit ratio include the following:

 * If you are using anonymous user caching (for example, for an Internet-facing site), users are regularly requesting content that has not yet been cached.
 * If you are using ASP.NET output caching for authenticated users, many users may have edit permissions on the pages that they are viewing.
 * If you have customized any of the **VaryBy\*** parameters on any page (or master page or page layout) or customized a cache profile, you may have configured a parameter that prevents the pages in the site from being cached effectively (For example, you might be varying by user for a site that has many users).

  |

**Note : **

For the ASP.NET output cache, all pages are cached for a fixed duration that is 
independent of user actions. Therefore, there are flush-related monitoring events.

For more information about the ASP.NET output cache, see [Output Caching andCache Profiles](http://go.microsoft.com/fwlink/p/?LinkID=121543)(
[http://go.microsoft.com/fwlink/p/?LinkID=121543](http://go.microsoft.com/fwlink/p/?LinkID=121543))
or [cache Element for caching (ASP.NET Settings Schema)](http://go.microsoft.com/fwlink/p/?LinkId=195986)(
[http://go.microsoft.com/fwlink/p/?LinkId=195986](http://go.microsoft.com/fwlink/p/?LinkId=195986)).

**Monitoring object cache performance**

 * The object cache is used to **store metadata about sites, libraries, lists, list
   items, and documents** that are used by features such as site navigation and 
   the Content Query Web Part.
 * 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 can monitor the effectiveness of the cache settings by using the [performance ](https://sharepointtechnicalsupport.com/category/performance/)
   monitors that are listed in the following table.

**SharePoint Publishing Cache counter group**

  |  **Counter name ** |  **Ideal value or pattern ** |  **Notes ** |  
 |  Total number of cache compactions |  0 |  If this number is high, the cache size is too small for the data being requested. To improve performance, increase the size of the cache. |  
 |  Publishing cache flushes / second |  0 |  Site owners might be performing actions on the sites that are causing the cache to be flushed. To improve [performance ](https://sharepointtechnicalsupport.com/category/performance/)during peak-use hours, make sure that site owners perform these actions only during off-peak hours. |  
 |  Publishing cache hit ratio |  Depends on usage pattern. For read-only sites, the ratio should be 1. For read-write sites, the ratio may be lower. |  If the ratio starts to decrease, this might be caused by one or more of the following:

 * The [cache ](https://sharepointtechnicalsupport.com/category/cache-2/)was recently flushed or compacted.
 * Users are accessing content that was recently added to the site. This might occur after lots of new content is added to the site.

  |

### Share this:

 * [  X ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=twitter)
 * [  Facebook ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=facebook)
 * [  WhatsApp ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=jetpack-whatsapp)
 * [  Email ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?subject=%5BShared%20Post%5D%20Cache%20Monitoring%20SharePoint%202013&body=https%3A%2F%2Fsharepointtechnicalsupport.com%2F2015%2F05%2F03%2Fcache-monitoring-sharepoint-2013%2F&share=email)
 * [  Telegram ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=telegram)
 * [  LinkedIn ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=linkedin)
 * [  Tumblr ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=tumblr)
 * [  Pinterest ](https://sharepointtechnicalsupport.com/2015/05/03/cache-monitoring-sharepoint-2013/?share=pinterest)

### Like this:

Like Loading…

### _Related_