Configuring caches

To configure output caching basic knowledge about ASP.NET and SharePoint output caching is required. These pages help you get started:


Cache profiles

This section describes cache profiles used by Eneta portal. Parameters are custom cache parameters asked when creating SharePoint output cache profiles. Duration for all these profiles is 900.

  • Articles
    Parameters: Announcement;AnnouncementModified;Role
  • Blogs
    Parameters: BlogEntryModified;Role
  • Common buffer
    Parameters: Role
  • BlogEntry
    Parameters: BlogEntryModified;Role;HtmlControl
  • BlogDetailView
    Parameters: LastBlogEntryModified;HtmlControl
  • BlogsList
    Parameters: BlogEntryModified;HtmlControl
  • ArticleDetailView
    Parameters: AnnouncementModified;HtmlControl;Role
  • ArticleList
    Parameters: LastAnnouncementModified;HtmlControl
  • NewsList
    Parameters: LastNewsModified;HtmlControl
  • EventsList
    Parameters: LastEventModified;HtmlControl
  • EventDetailView
    Parameters: EventModified;HtmlControl


Measuring output cache

Output cache does not work safe when it is just turned on. Output cache must be measured to see if it gives effect and to make sure it doesn’t degrade performance of portal application. Output cache can be measured using Windows Performance Monitor tool that ships with Windows Server. If you are not familiar with Performance Monitor then the following links may help you:

You have to measure the following performance counters:

  • total number of objects added,
  • total object discards,
  • cache hit count,
  • cache hit ratio.

These counters and their “good” values are described in blog post referred above. If cache hit ratio is over 85% and more pages are added than discarded (like shown on chart in referred blog posting) then your caches perform very well. If number of object discards is a lot lower than objects added then content is probably cached for too long time and you have to shorten the time the pages are kept in cache. SharePoint cache uses server memory or database (depends how you have configured your web applications) and keeping pages in memory too long means that server has less memory to use for requests, database queries and other operations.

It is recommended to keep performance monitor running for 8-10 hours during active portal usage period to collect counter values that give you idea how site performs with usual load.

Last edited Dec 1, 2010 at 12:56 AM by gpeipman, version 2


No comments yet.