TOP 10 Tips for Improving SharePoint 2010 Performance
TOP 10 Tips for Improving SharePoint 2010 Performance
1. Plan:
Planning for authentication, performance, capacity and future growth, either at the initial design phase or after deployment is one of the most important exercises of building and maintaining SharePoint 2010. SharePoint is deceptively complex and lack of planning both in the initial stages as well as the long term can cause pain points within service applications, storage and server resources that start small and become major headaches in the future.
Resources:
- Initial deployment administrative and service accounts (SharePoint Server 2010)
- Hardware and software requirements (SharePoint Server 2010)
- Plan authentication methods (SharePoint Server 2010)
- Plan browser support (SharePoint Server 2010)
- Performance and capacity management (SharePoint Server 2010)
- SharePoint Server2010 capacity management: Software boundaries and limits
2. Use site quota or the Quota template for Site Collections or Mysites
This is the place which a SharePoint administrator has to keep an eye. The Site collections Can Grow Big and might Cross 100 GB Max. To Maintain proper working environment and to make easy backups it strongly recommended to have limitation on the Site growth. SharePoint isn’t capable of self-managing the size of its database and with users constantly adding new content the data store will continue to the grow if you don’t impose defined limits. Quotas will really help in maintain the health of the environment and also keep the databases in Supported stated. The site quota template varies according to the environments.
Resources:
- Plan quota management (SharePoint Server 2010)
- Create, edit, and delete quota templates (SharePoint Server 2010)
- Manage site collection storage limits (SharePoint Server 2010)
3. System Health and Availability of Resources:
When we are looking at SharePoint 2010, Its not he Site collections or the My sites which will consume and store content. There are services which will consume the Storage and resources. A good Administrator will also look into other aspects as when looking at other overheads like Enterprise search, User Profiles, Web Analytics, Health monitoring which will impact performance and latency. The administrator should plan the requirements of the environment.
Resources:
- Monitoring overview (SharePoint Foundation 2010)
- Configuring monitoring (SharePoint Foundation 2010)
- Viewing reports and logs (SharePoint Foundation 2010)
- Solving problems and troubleshooting (SharePoint Foundation 2010)
- Monitor health and performance of a virtual environment (SharePoint Foundation 2010)
- Health Monitoring for SharePoint 2010
- Monitoring overview (SharePoint Server 2010)
4. Monitor Recycle bins which consumes space outside of Site collection
There are 2 stages for the recycle bin. The first stage is used for user recoverable content and is stored within the site collection. This consumes space against the site collection quota. User recoverable content has a default limit of 30 days, and then it is moved to the second stage recycle bin. The second stage recycle bin is used by the site collection administrator and/support staff to recover content that may have been deleted and/or expired from the first stage recycle bin. It consumes 50% of SharePoint’s total quota size, so you should enforce a quota or it will continue grow out of control.
Resources:
- Configure Recycle Bin settings (SharePoint Foundation 2010)
- Protecting content by using recycle bins
- Protecting content by using versioning
5. Site collections, its necessity and performance
The only type of sites that can be moved between content databases are site collections. We can easily achive the stability by managing site collections and database storage can provide flexibility, but also puts additional boundaries within the environment. Maintaining a site collection structure based on teams, projects and departments will allow individual sites to grow organically. It also imposes some security limitations and gives each site collection a different look and feel. if we understand the requirement of a team or project that can really help in maintaining and managing the site collections.
Resources:
- Plan sites and site collections (SharePoint Server 2010)
- Sites and site collections overview (SharePoint Server 2010)
- Site navigation overview (SharePoint Server 2010)
- Plan site navigation (SharePoint Server 2010)
6. SharePoint 2010 and User Profile Service
The User Profile service application stores information about users in a central location. Social computing features use this information to facilitate productive interactions which enable users to collaborate efficiently. In order to provision My Sites, enable social computing features such as social tagging and newsfeeds, and create and distribute profiles across multiple sites and farms, you must enable the User Profile service application contain detailed information about individuals in an organization. A user profile organizes and displays all of the properties related to each user together with social tags, documents and other items related to that user. We need to make sure that Proper accounts are added and correct OUs are selected from the domains. We need to monitor whether the user profiles are being imported properly or not. Assigning the correct organizational units/containers within the Active Directory structure will allow the User Profile Service to only target the required users and groups. This will prevent SharePoint from accessing service and other miscellaneous accounts and ensure the optimal performance of the User Profile Service.
Resources:
- Plan for profile synchronization (SharePoint Server 2010)
- Troubleshoot User Profile Synchronization Service start issues (SharePoint Server 2010)
- Troubleshoot profile synchronization configuration issues (SharePoint Server 2010)
7. External search Vs SharePoint OOB and FAST Search for SharePoint 2010
SharePoint Can index the external sites and internet and provide the query results which is beneficial for an organization to find content in easy and effect way. But it has huge impact on the Performance. if you are using OOB SharePoint Search then the total size varies from 15% to 25% of storage for index file. If you are using FAST Search for SharePoint you can add 10% more for the size of the SharePoint OOB index. These sizes are inductive. But the Administrator has to monitor this carefully and Create content sources and add the content to the environment. But it is always recommended to have reserved space for these content sources when planning the Search.
Resources:
- Plan search topology
- Performance and capacity test results
- FAST Search Server 2010 for SharePoint Capacity Planning
- Search scopes in FAST Search for SharePoint part 1
- Monitor FAST Search Server 2010
- FAST Search Server 2010 for SharePoint Capacity Planning
- Troubleshooting Best Practices for FAST Search Server for SharePoint 2010 Installation
- Troubleshooting: FAST Admin DB
8. Understand SharePoint limitations and planning long term goals.
SharePoint 2010 is extremely Scalable and flexible for the deployment. Microsoft has provided some limitations and Boundaries for SharePoint. We need to keep in mind the scenarios and best practices while deploying SharePoint in the Environment. First we need to do lab testing but this will not give actual results. The good starting point is to follow the guidelines while deploying the Customizations, Solutions. This will ensure the System stay in tact and perform as expected.
Resources:
- Performance and capacity management (SharePoint Server 2010)
- SharePoint Server 2010 capacity management: Software boundaries and limits
- Plan search topology
- Plan sites and site collections (SharePoint Server 2010)
- Developer Best Practices Resource Center | SharePoint 2010
- Inside SharePoint: SharePoint 2010
- Governance overview (SharePoint Server 2010)
9. Storage for planning is crucial
Data Storage is one of the Key and important thing in SharePoint performance. Poor storage for content databases and Service application databases will really cause performance hit. Understanding the Storage requirements for SharePoint is key. If the SharePoint access the Databases and the file stores properly we can expect the high Performance level over the period of time. The SharePoint content has less impact on the overall performance but it is good to start from here.
Resources:
- Enterprise content storage planning (SharePoint Server 2010)
- Document library planning (SharePoint Server 2010)
- Plan for disaster recovery (SharePoint Server 2010)
- Storage and SQL Server capacity planning and configuration (SharePoint Server 2010)
10. SQL Server Deployment, the heart and brain of SharePoint.
If you are planning for robust and reliable SharePoint Environment, Plan the SQL server accordingly. A Proper SQL server can Mean the difference between a high performance or a constantly failing systems. Make sure that SQL Deployment is met withe best practices and meets the resources. This includes Memory, CPU and disk space. SQL configuration is tuned for optimum performance in SharePoint Deployment in a Large SQL Cluster Sharing resources. Make sure SharePoint databases are set to simple recovery model and correct collation. Make sure we have the adequate disk space for the log files. Ensure the databases are being taken backup.
Resources: