SharePoint 2013 is very robust and powerful. All of this robustness and power comes with a price: resources. If you have twenty available servers and can scale-out like crazy, you shouldn't have any problems. However, most o...

Buy Now From Amazon

Product Review

SharePoint 2013 is very robust and powerful. All of this robustness and power comes with a price: resources. If you have twenty available servers and can scale-out like crazy, you shouldn't have any problems. However, most of us don’t have that many servers at our disposal; especially for QA and development environments.
Therefore, it is important to tweak and configure SharePoint 2013 such that you get the performance and functionality without utilizing too many resources.

This guide explores various areas and options for Timer Jobs and Services such that minimal resource usage is achieved in both Development/QA environments as well as Pro-duction.

Check out the other optimization areas in Steve’s solution series or get them all together in Optimizing Your SharePoint 2013 Environments.


Similar Products

How To Create a WCF Web Service in SharePoint 2013 (SharePoint 2013 Solution Series)Optimizing SharePoint 2013: Logging (SharePoint 2013 Solution Series Book 14)SharePoint 2013 Strategies, Policies, and Best PracticesHow To Integrate BCS with Search in SharePoint 2013 (SharePoint 2013 Solution Series)How to Enhance the Search Box in SharePoint 2013 (SharePoint 2013 Solution Series Book 8)SharePoint 2013 and Windows Azure Integration StrategiesWorking with SharePoint 2013 Content Databases (SharePoint 2013 Solution Series Book 18)SharePoint Search Queries Explained: A guide to writing search queries in SharePoint 2013 and SharePoint OnlineSharePoint 2016 Search Explained: SharePoint 2016 and Office 365 Search On-Premises, Cloud and Hybrid for Search Managers and Decision MakersSynonyms and Sugar in SharePoint 2013 Search (SharePoint 2013 Solution Series Book 9)