Sharepoint 2013 distributed cache service
1 / 11

SharePoint 2013 Distributed Cache Service - PowerPoint PPT Presentation

  • Updated On :

SharePoint 2013 Distributed Cache Service. Steve Peschka Sr. Principal Architect Microsoft Corporation. Cache Service. There is a new distributed cache service in SharePoint 2013 based on Windows Server AppFabric Distributed Caching

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'SharePoint 2013 Distributed Cache Service' - sora

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Sharepoint 2013 distributed cache service
SharePoint 2013 Distributed Cache Service

Steve Peschka

Sr. Principal Architect

Microsoft Corporation

Cache service
Cache Service

There is a new distributed cache service in SharePoint 2013 based on Windows Server AppFabric Distributed Caching

It is used in features like authentication token caching and My Site social feeds

SharePoint 2013 uses caching features that cloud-based cache (Windows Azure Cache) does not support at this time, so only local cache hosts can be used

SharePoint ONLY supports the version of caching that it ships – you cannot independently upgrade it.

Cache service1
Cache Service

The config DB keeps track of which machines in the farm are running the cache service

It is all provisioned by SharePoint setup

A new Windows service – the Distributed Cache service – is installed on each server in the farm when SharePoint is installed

Cache service2
Cache Service

SharePoint installs and starts the Distributed Cache service on each server in the farm

  • It is enabled by default on all servers in the farm except for SQL

  • You can disable it on a server by using the Services on Server admin page in central admin, BUT – you should use the PowerShell cmdlets to gracefully control it

Cache setup
Cache Setup

The farm account is used as service account for Cache Service

Like user profile service in SharePoint 2010, during setup the service account should have elevated privileges (i.e. local admin)

After setup is complete you should lower the privileges for the account

Distributed cache in sharepoint 2013 default config
Distributed Cache in SharePoint 2013 (Default Config)

Distributed Cache service (Windows service)

Distributed Cache service (Windows service)

Distributed Cache service (Windows service)

Distributed Cache service (Windows service)

Distributed Cache service (Windows service)

Other Service Apps

Other Service Apps

Distributed Cache service (Windows service)

Other Service Apps

Cluster configuration stored in config DB

General cache server sizing guidelines
General Cache Server Sizing Guidelines

Cache servers use about 50% of allocated memory for overhead

The maximum recommended RAM per cache server is 16GB

Above that will work, but when flushing cache it may take so long to clear out that the server can appear hung

You should allocate 2GB RAM to the OS

That leaves a maximum of 14GB for cache:

7GB storage and 7GB for overhead

Sizing info will be available that will help you determine how much overall cache storage your farm requires

In the example above, take total storage required / 7GB = # of cache servers needed

Cache implementation
Cache Implementation

We recommend that you use servers dedicated to caching – not shared with WFE or service applications

The data as a whole is divided and distributed between all cache servers

If a server goes down unexpectedly, user performance will suffer until other servers become populated with the data that was lost

This process can be accelerated with:

User Profile Service - Feed Cache Repopulation Job timer job

Clear-SPDistributedCacheItem, Update-SPRepopulateMicroblogLMTCache and Update-SPRepopulateMicroblogFeedCache PowerShell cmdlets

If you know you are going to bring a cache server down you should do so gracefully with the Stop-SPDistributedCacheServiceInstancecmdlet

This copies the data to other cache servers to minimize the performance impact

Cache server performance
Cache Server Performance

There are hundred(s) of perf counters; there are also counts exposed via developer’s dashboard

# of reads

# of writes

# of hits

# of misses

time for read

time for write

Total I/O (how much data has been transferred in a given period of time)

Cache service health
Cache Service Health

The following health rules have been created to help you track the Cache Service (look in the Availabilitysection for most):

One of the cache hosts in the cluster is down (Availability)

Firewall client settings on the cache host are incorrect (Configuration)

Cache host is in throttled state(Availability)

The high availability node for SharePoint distributed cache is not available(Availability) – happens when there are less than 2 servers running the cache service

There exists at least one cache host in the cluster, which SP doesn't know about (Configuration) – happens when the cache service is disabled in SharePoint but AppFabric Caching Service is running on the machine

Cached objects have been evicted(Configuration) – indicates eviction happened across the cache cluster. Not bad in and of itself but may be a clue if it happens frequently and/or there are perf issues

Distributed cache service

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.