latest updates from easySERVICE™
Microsoft SharePoint is the fastest growing product in Microsoft history. Its adoption rate has been exponential with millions of documents being stored daily. With its growth critical documents and procedures are now being stored in SharePoint. It is fundamental that SharePoint maintains its healthy status, and application performance is a key component for a successful deployment and adoption of SharePoint.
These steps are there to help you with SharePoint performance to help organizations better understand the different ways and places SharePoint performance can be improved. SharePoint deployments are a combination of applications, services and databases where delivering a scalable, dynamic and efficient portal implementation can be a challenging task for even the most experienced IT professionals. Improvements can be made within or outside of the SharePoint infrastructure.
Step 8 Take Advantage Of Caching
SharePoint serves up a lot of data but not all of it is retrieved in real-time from the database. Much of the content requested by users can be cached in memory, including list items, documents, query results and web parts. How, when and by what rules SharePoint caches content is governed by cache profiles which can be configured for a single site or an entire site collection. Each cache profile is comprised of settings which tell the system which content to cache, who to cache it for, when to release it and when to check for updated content.
Site administrators can configure their own cache profiles to meet different user needs. Anonymous users, for example, can be assigned one set of cache policies while authenticated users are assigned another, allowing content editors to get a more recent view of content changes than general readers. Cache profiles can also be configured by page type, so publishing pages and layout pages behave differently, and administrators have the option to specify caching on the server, the client, or both.
In addition, the SharePoint Object Cache can significantly improve the execution time for resource-intensive components (such as the Content Query Web Part). By determining in advance whether or not to check for new query results on each request or to use a set of previous results stored in memory, queries which cross site boundaries can be prevented from making excess demands on the database. Large objects which are requested frequently, such as images and files, can also be cached on disk for each web application to improve page delivery times.