Disabling the Distributed Cache Service

I ran into a small performance issue when running Project Server Service and Distributed Cache Service on the same server and wanted to pass this info on to the community. Some of you may find it interesting.

After installing and configuring SharePoint 2013 I have noticed that Distributed Cache Service is enabled by default.  I never thought much about what it does until recently. While reading about the purpose of Distributed Cache Services, the article stated that Distributed Cache Service should not be running on the same server that runs Project Service, Excel Service, SQL Server or Search Service.  What?  I’m I the last person on earth that just found this out?  I hate to be the last to know these things!

Distributed Cache Service is used for with SharePoint services such as Newsfeeds, OneNote client access, Security Trimming, Page load performance and Authentication.  It also grabs 10% or more of physical memory, which can an impact on performance.  The cure to remove is easy. Simply stop the services using SharePoint Admin or PowerShell. I stopped Distribute Cache Service on my SharePoint servers and Project Server does seem slightly more responsive.

So as a best practice when installing SharePoint using the SharePoint 2013 Product Configuration Wizard or when using a PowerShell cmdlet that uses New-SPConfigurationDatabase (by default Distributed Cache services is started) is to stop the Distributed Cache Service after the SharePoint farm is provisioned.  Also the New-SPConfigurationDatabase cmdlet has a switch called –SkipRegisterAsDistributedCacheHost that prevents the Distributed Cache Service from loading, so I have included this switch in my PowerShell scripts.

Here is a reference link about Distributed Cache Service.

Hope that helps!

Avatar photo
Written by Michael Wharton
MVP, MBA, PMP, MCT, MCTS, MCITP, MCSD, MCSE+I, MCDBA. Michael Wharton is a Project/SharePoint Consultant and Trainer. Michael’s career started as a software developer before moving into project management. His passion to improve project management processes began in 2003 using tools like Project Professional and Server. Since then he has trained hundreds of project managers and implemented Project Server in over twenty-five PMOs. He has passed over forty Microsoft certification exams giving him a solid technical background with Project and SharePoint Server. Michael is active in the community. He is the past President-Elect and past Director of Programs for the NC Piedmont PMI, board member of the Triad SQL Server User Group, Triad Developers Guild and Enterprise Architect Roundtable. He is currently writing a book about implementing Portfolio Management using Project Server 2013.
Share This Post
1 Comment
  1. Thanks for sharing Mike. Great post.

    Just like any SharePoint service application planning, I would plan for which service applications & associated services needs to run on which servers in the farm. Every service application has its own benefits and hence enterprise architectural planning go for long.

    Based on the business requirements and farm architecture, I would stop the service on servers running Project Server Service Application and services, but keep it active on other servers in the farm.

    In my SharePoint / Project Server 2013 farm architectures, I would use these Service Application planning resources.

    1. Plan service deployment in SharePoint 2013 [Also talks about server recommendations for each service application]

    2. Planning worksheets for SharePoint 2013

    3. Services on server install workseet for traditional SharePoint Server 2013 topologies

    Faisal Masood – PMP, CCNA, MCSE, MCITP, MCTS, MCSA, MOS
    Twitter: https://twitter.com/faisalmasoodcom
    LinkedIn: https://www.linkedin.com/in/faisalmasoodcom

    Professional Services on SharePoint, Project Server EPM / PPM, Office365, Azure and more

Leave a Reply