Distributed Cache Service in Three-tier Farm

Hello and welcome to my new blog!
Let's start with your possible SharePoint architecture in production environment.
Probably you may decide to plan your servers like three-tier farm:

So you have three servers:

• Database
• Application (back-end)
• Front-end

In application server you may install Search and/or Excel services, and then you'll see that each *.aspx page requests waiting about 6-7 second.

You may find many threads in forums, for example, this and this.

The reasons is distributed cache service, which is executes on application server. Microsoft recommends that servers running Excel Services, and Search services not be used as cache hosts. So you need to move distributed cache to front-end.

Write your own ps-script (depends on your service IDs) and run in application server. Get you service ID with:

  Get-SPServiceInstance | where {$_.TypeName -match 'Distributed'} | select typename, id, server  

and remove service instance from server:

$serviceInstance = Get-SPServiceInstance | where {$_.ID -eq "<your service GUID>"}  
$serviceInstance.Delete();  
Remove-SPDistributedCacheServiceInstance  

Then just run in front-end server:

 Add-SPDistributedCacheServiceInstance  

And requests freeze will be gone!