- Blob Cache has been set for 24 hours
Parameter needs to be set is “max-age” under blob tag in web.config file of the application
- Http Response header removal to enable caching of the web application
1. Param Expire 0
- CSS Registration under “<Sharepoint:CSSRegistration” tag which helps to cache the css in SharePoint 2013
- Cache Profiles, Site Collection Object Cache, Site Output Cache, Page layout cache
- Trouble Shooting
1. Under “Safe Mode” callstack =”True” but could impact the performance of the application
2. Under “Compilation” tag in “web.config” setting Debug=”True” will impact and disable the caching of the application on “Client Side” and “Server Side”
3. Set Connection string under connection settings in web.config file using “Secure Connection string” command for more search on Google
- Set Default time zone of the application under SharePoint 2013 otherwise it will be running timer jobs as per the server time zone
1. For e.g.: if server is in USA and Client is in India the timer job and Default time zone is not set to the client country time zone then the timer jobs will be referencing the server timings of the hosted country and which will run at any time perhaps the Indian Market hours which could impact the performance of the application and can be faced by the end users complaining of slowness of the application.
- Secure Store Service
1. To share the credentials to developers without providing the confidential username and password by proving the secure store service key to the developer will do the job. The key will authenticate the BDC application to communication with external databases with the auto generate key by SharePoint 2013 under secure store service
- List View threshold should not exceed the limit of 5000, however 30 million records can be saved in the list
- Search Query v/s CAML query
1. Search Query is used to fetch large number of data
2. CAML query cannot be used to fetch large no of data
3. Search Query: For an instance we have to crawl 3 columns from list which will create 3 search properties to query data using managed metadata service via using search query
- Below Path to create search query crawl
1. CA->Managed service application->Search Service application->Search Schema
- App pools recycle introduced in SharePoint 2013 it was not present in SharePoint 2007
1. Http.sys kernel mode driver accepts the request from client browser
2. W3wp creates queue as per app pool, which will have two queues Input and Output queue.
3. Whenever an app pool is recycled the old w3wp will stop taking client request and the new request will be diverted to the newly created w3wp. If old w3wp consists of any request and all the request gets completed under the declared Shutdown time limit in IIS will forcibly close the old w3wp. The only drawback of app pool recycle is whenever the request switches to new w3wp the whole process of caching starts from the beginning which slowdowns the process of load site on client end and users observes a slowness while loading the website.
- HTTP 1.1 SP 2013
1. 1.0-> 4 concurrent connection to minimize the overhead of response
2. 1.1-> Keep Alive (gives response faster)
3. 2.0-> used by Google
- Health Usage and data collection service consumes more resource which impacts the server performance under CA
- Optimization of web part fetching large list
1. Where clause have to be assigned on Indexed column of the list
2. Having Index column and where clause assigned to the same column in the list, however it’s still affecting the performance while loading the web part then check the threshold limit of list that it has crossed 5000.
3. CAML query without where clause
