Unlike SharePoint 2010, where the cache was a way to store information and each server had its own, in SharePoint 2013 had a mechanism of distributed caching that spread all the data in the farm.
This service is based on the Windows Server AppFabric 1.1 caching model (for more information: http://msdn.microsoft.com/en-us/library/hh351389.aspx ).
Off course use the Distributed Cache Service take some benefits for the following features:
- Authentication: the service will stores the security token used by the Security Token Service for use by any web server in the server farm. In this way, every time a user ask to be authenticated in a web server, the web server will get the token from the cache cluster. In SharePoint 2010 was used a trick know as: sticky sessions
- Socials: My Sites contain the new Microblog and Newsfeeds features. These features allow users to engage in short, public conversations, and keep up-to-date on activities from content and people in which they are interested. This feature take a strong use of DCS, usualy every update will register into the service and will may used. (for more information: http://technet.microsoft.com/library/jj219700(office.15).aspx)
- OneNote Client Access
- Security Trimming
- Page Load Performance: SP 2013 include a new framework that improves page load performance by only downloading those portions of the page that have changed. The name of this feature is Minimal Download Strategy (MDS). It is by default enable on Team site, Community site and a few others site template. When it is enable all pages is rendered by the /_layouts/15/start.aspx page. I will write a post to explain how it works. For now I past to you what Microsoft wrote in the msdn: <
he minimal download strategy will use a single .aspx file (start.aspx) for your pages, with the actual URLencoded in the text following the hashmark (‘#’). When navigating from page to page, only the changes between two compatible pages will be downloaded. Fewer bytes will be downloaded and the page will appear more quickly.>> - Search
The DCS can run in two modes:
- Dedicated mode: This is Microsoft's recommended mode. All thse services are stopped on the server except DCS. Microsoft recommends that no more than 16 GB of memory should be allocated to the DCS.
- Collocated mode: Microsoft does not recommend this mode and any of the following services or application should not run on the same server:
- SQL Server 2008 or 2012
- Search engine
- Excel Services
- Project Server services
Following the Windows PowerShell cmdlets that you can use to manage the DCS:
- Add-SPDistributedCacheServiceInstanceOnLocalServer
- Clear-SPDistributedCacheItem
- Get-SPDistributedCacheClientSetting
- Remove-SPDistributedCacheServiceInstanceOnLocalServer
- Set-SPDistributedCacheClientSetting
- Stop-SPDistributedCacheServiceInstanceGracefullyOnLocalServer
- Set-CacheHostConfig
Some references:
No comments:
Post a Comment