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!