SP 2013 made
infrastructure changes to speed up the rendering of pages like
·
Web server
caching improvements
o
In SP 2010,
Each SharePoint server had its own cache.
o
If another
server get the second request, the content retrieved from the content database,
even though the content was still in the memory of the first server.
o
SP 2013 uses
distributed cache so that no connection to content DB for second request.
o
SP 2013 distributed
cache service (DCS) uses Windows Server AppFabric 1.1 catching model.
o
DCS uses the
following ports (22233, 22234, 22235, 22236)
o
Below
components of SharePoint 2013 that use distributed
§
Feeds: This cache
stores activities and conversations for use by the newsfeeds on a user’s My
Site.
§
Logon
Tokens:
§
Search: Used
by the Content Search Web Part (CSWP) new in SP 2013.
o
It can start
from CA à Services On Server à
start the Distributed Cache service.
o
Server from
which above service is started is known as cache host. And a group of cache
host known as cache cluster.
o
To have
Distributed Cache working on more than one server, the first server with
Distributed Cache needs to have its firewall set to allow for inbound Internet
Control Message Protocol.
o
When start
the this service in a new SP server it joins the cache cluster. And distributed
cache spans to all cache hosts.
o
Memory for
Distributed Cache service is 10 percent of total physical memory by default
o
Half of
above memory used for data storage known as cache size.
o
Other half
used for memory management.
o
DCS can run
in one of the following two modes
§
Dedicated
Mode – (Recommended)
·
DCS is
started and all other services are stopped on the server.
·
Not more
than 16 GB of memory should be allocated to the DCS with at least 2 GB of
memory reserve for other services.
·
More than 16
GB of memory to the DCS might slow the response of the server.
§
Colocated
Mode – (Not Recommended)
·
Distributed
Cache service is started along with other services on the server.
·
All
nonessential services should be shut down to reduce the memory competition
while using this mode.
·
Not
recommend to start any of below service with DCS.
o
SQL Server
2008 or SQL Server 2012
o
Search
service
o
Excel
Services in SharePoint
§
Project
Server services
o
Don’t use applications to manage the DCS. AppFabric
provides administrative tools on the Start menu or use the SharePoint 2013
Management Shell.
o
DCS can be
affected by unplanned shutdown or power failure of server which can leads to
unrecoverable state.
o
Few
PowerShell commands to manage DCS.
§
Add-SPDistributedCacheServiceInstance
§
Clear-SPDistributedCacheItem
§
Get-SPDistributedCacheCllientSetting
§
Remove-SPDistributedCacheServiceInstance
§
Set-SPDistributedCacheClientSetting
§
Stop-SPDistributedCacheServiceInstance
§
Update-SPDistributedCacheSize
·
Introduction
of a minimal download strategy
o
SP 2013
improves the page load performance by downloading those portions which actually
changed.
o
This new
feature is active by default at web level and works with AjaxDelta control in
master page. (Not enable for publishing
sites)
o
By
activating, it sets the object EnableMinimalDownload property of web.
o
This can be
disable in two other ways to prevent the use of MDS.
§
Add
“PageRenderMode” control in master page and set RenderModeType to standard.
§
All controls
in Microsoft.Sharepoint.dll have the attribute “MdsCompliantAttribute” which
must be set to use MDS. But controls under Microsoft.SharePoint.Publishing.dll
don’t have that attribute.
§
If you have
migrated to SP 2013, then your custom controls will not automatically have this
attribute. Need to recompile, reinstall the solution files.
o
·
A new Theme
engine
o
In SP 2010: on
publishing sites we could create new themes by using word 2010, PowerPoint 2010
or theme builder and uploading .thmx file into theme gallery.
o
In SP 2013:
Themes are based on HTML5. So MS office no longer helpful for this.
o
We can
change image, colors, master pages and also see preview before apply it.
o
By default
18 themes are available.
·
Improved
support for mobile devices
·
Implementation
of HTML5 and increased web browser support
No comments:
Post a Comment