Keynotes for Distributed Cache on SharePoint 2013


My colleague Hector has created a very good article by compiling different issues with Distributed Cache.
You can read the orginal article below link:
http://blogs.msdn.com/b/calvarro/archive/2013/08/29/points-to-consider-with-distributed-cache-on-sharepoint-2013.aspx

Here is the key notes:

  • NEVER admin the distributed cache from the admin console
  • Maximum capacity of memory is 16 GB per host cache
  • Dynamic memory is not supported in SharePoint 2013 environments nor APP fabric servers
  • The prodcuct after being installed allocates 10% of the physical RAM memory available at the sever. It can be configured following the next point.
  • It’s recommended to allocate 2 GB for other services.
  • It’s not supported to develop code against the Distributed Cache of SharePoint 2013.
    “If you are using custom applications in SharePoint Server 2013 which use the AppFabric client APIs, or are creating custom caches, you should create a separate AppFabric cache cluster to support your custom applications. Do not use the AppFabric cache cluster supporting your SharePoint Server 2013 farm. Run your separate AppFabric cache cluster for your custom applications on separate servers from the servers dedicated to your SharePoint Server 2013 farm.
    http://blogs.msdn.com/b/calvarro/archive/2013/06/05/supportability-of-custom-developments-in-sps-2013-and-appfabric-cache.aspx
  • Install the latest APP Fabric CU if possible. Right now we are in CU 4
Advertisements

About bpostaci
Sr. Support Escalation Engineer in Microsoft.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: