As you make plans to implement Distributed Cache service, you need to keep in mind that there are two modes offered:
- Collocated mode the service operations along with other services on the application server.
- Dedicated mode the service operates alone so it is stopped on the application server. This is the most common mode used.
Windows Server AppFabric will be installed when the SharePoint Server 2013 Preview installer runs. This is the best method of installing it. If you already have it installed prior to running the prerequisite installer you will need to uninstall it. The administrator will determine if it should be installed manually or not. If so, they will need to install the CacheAdmin, CacheClient features, and CachingService.
It is very important to understand the concepts of Distributed Cache. The Distributed Cache services memory allocation is going to default to a value of 10% of the total physical memory when you install SharePoint Server 2013 Preview. The administrator is able to change that amount of allocation though. If you run in dedicated mode, only up to 16 GB can be allocated for it.
It is recommended that you reserve 2 GB of memory for any other services that happen to be running on the server. Assign what remains to the Distributed Cache Service. It can run with either a virtual or physical server. Don’t rely on Dynamic Memory to manage the shared memory resources. You will need to set it manually.
You don’t want to start and stop Distributed Cache Service as that will make it an unreliable resource. When you initially configure it with SharePoint Server 2013 farm, you want do the steps in this sequence:
- Run the Configuration Wizard so that all of the servers are part of that farm. This will start it on all web servers and application that belong to that server farm.
- Perform all other farm configuration steps that are required.
Confirm that Distributed Cache Service is running on all of the servers of the farm. Proceed to stop it for any server that isn’t part of that arrangement.