locked
page output caching in sharepoint 2010 RRS feed

  • Question

  • We enabled page output caching on one of the internet facing sites in qa for anonimous users.

    Are there in cons to this except increased memory consuption and inconsistancy in rendering due to load balanced 2 frontend servers.

    Below link explains official pros and cons. are there any issues with hardware memory etc for caching in internet facing sites?

    and what should be the ideal settings for cache profile for internet facing sites? By default it shows 180 seconds.

    When we tested our site in qa after caching, it improved the performance real good on subsequent page requests.

    http://office.microsoft.com/en-us/sharepoint-server-help/improve-page-rendering-by-configuring-output-caching-HA101785628.aspx


    sharepointer
    Wednesday, December 29, 2010 11:07 AM

Answers

  • Enabling page caching is a good thing, especially it is working for you and the situation you are describing is ideal. You should really monitor it to see your cache hit ratio. This article lists the performance counters to monitor: http://technet.microsoft.com/en-us/library/ff934623.aspx 

    In terms of the best settings, it really depends on the types of users you have and their patters, and it also depends on the type of content and the timeframe with which it changes. If you have low hit rate, you might try increasing 180 to something higher.

    Anything that increases the number of cache instances (eg number of WFE servers) is just something you should plan for. And yes, cache will consume RAM.

    And last, you really should PLAN what you are trying to optimize, and how much you want to optimize it. Consider other options like Blob cache, object cache, browser cache, etc.

    Hope this helps!


    Living the SharePoint dream...
    • Marked as answer by GuYuming Wednesday, January 5, 2011 7:00 PM
    Monday, January 3, 2011 8:47 AM
  • Amit, this is nearly impossible to measure without knowing usage patterns and content lifetime, and unique permissions over the content. You will also need the number of pages. But ofcourse you are only planning, and capacity planning is anongoing exersize.

    As a general .NET rule of thumb, cache stores twice the rendered page size in KB + 32KB in RAM. So a 10KB page will take 52KB of RAM. I am not aware of any other statistics on these questions, but this may help: http://www.astaticstate.com/2010/06/sharepoint-2010-cache.html

    You really have to test this scenario out if you have the time and money to do so.


    Living the SharePoint dream...
    Tuesday, January 4, 2011 11:12 AM

All replies

  • Hi,

    take a look at this links:

    Output Caching and Cache Profiles:http://msdn.microsoft.com/en-us/library/aa661294.aspx
     

    also take a look at this:Optimize a SharePoint Server 2007 Web Content Management Site for Performance (it applyes also to sps2010) http://msdn.microsoft.com/en-us/library/bb727371(v=office.12).aspx

    The second link its very usefull.

    Hope it helps

    Rodrigo Pinto,SharePoint Specialist, Evangelist
    http://www.sharepointpt.org
    SharePointPt Founder
    @Scoutmanpt

    Monday, January 3, 2011 1:31 AM
  • Enabling page caching is a good thing, especially it is working for you and the situation you are describing is ideal. You should really monitor it to see your cache hit ratio. This article lists the performance counters to monitor: http://technet.microsoft.com/en-us/library/ff934623.aspx 

    In terms of the best settings, it really depends on the types of users you have and their patters, and it also depends on the type of content and the timeframe with which it changes. If you have low hit rate, you might try increasing 180 to something higher.

    Anything that increases the number of cache instances (eg number of WFE servers) is just something you should plan for. And yes, cache will consume RAM.

    And last, you really should PLAN what you are trying to optimize, and how much you want to optimize it. Consider other options like Blob cache, object cache, browser cache, etc.

    Hope this helps!


    Living the SharePoint dream...
    • Marked as answer by GuYuming Wednesday, January 5, 2011 7:00 PM
    Monday, January 3, 2011 8:47 AM
  • Suppose we have 50+ site collections in a web app for internet facing sites and we want to enable page caching , how much memory will be required for 2 frontend servers?

     


    sharepointer
    Tuesday, January 4, 2011 10:00 AM
  • Amit, this is nearly impossible to measure without knowing usage patterns and content lifetime, and unique permissions over the content. You will also need the number of pages. But ofcourse you are only planning, and capacity planning is anongoing exersize.

    As a general .NET rule of thumb, cache stores twice the rendered page size in KB + 32KB in RAM. So a 10KB page will take 52KB of RAM. I am not aware of any other statistics on these questions, but this may help: http://www.astaticstate.com/2010/06/sharepoint-2010-cache.html

    You really have to test this scenario out if you have the time and money to do so.


    Living the SharePoint dream...
    Tuesday, January 4, 2011 11:12 AM
  • Thanks Radi for your help on cache. Now we can decide on how much hardware may be required if we want to enable cache for all sites.
    sharepointer
    Tuesday, January 4, 2011 11:26 AM
  • Hi Radi,

     

    How can we check in prod if page is taking request from caching or from database? we have 180 seconds interval for output cache for anonimous users in sharepoint 2010 internet facing sites.


    sharepointer
    Wednesday, January 19, 2011 3:39 PM