Friday, December 11, 2009

Sharepoint 2010 Top 10 : Performance & Hosting

Performance Controls
  1. Microsoft SharePoint Server 2010 provides two different performance controls. – Throttling & Large-list settings
  2. Throttling provides a way to control server resources and is designed so that the server can be protected from overload during peak business hours.
  3. Through throttling settings, SharePoint Server 2010 provides a way for administrators to determine the level at which the server will go into throttling mode. Every five seconds, a job runs that checks server resources compared to configured levels. By default, Server CPU, Memory, Request in Queue, and Request Wait Time are monitored. After three unsuccessful checks, the server enters a throttling period and will remain in this state until a successful check is completed. Throttling can be configured per Web application and is enabled through the Central Administration user interface or through a Windows PowerShell™ command.
  4. Throttling is a new capability in 2010 that essentially checks resource usage on the local server and when monitored KPI’s exceed administrator defined thresholds SharePoint will issue out 503 errors to new users until the server state improves. This ensures that existing requests will be completed before new requests are accepted. Throttling is configured on a per web app basis and by default will monitor CPU and memory utilization, Request Wait Time, and Requests in Queue.
  5. Large-list settings provide a way to limit the different queries within a list to ensure that performance is not degraded when users query a list that contains many items.
  6. SharePoint Server 2010 has the ability to support up to 50 million items within a SharePoint list;SharePoint Server 2010 provides several different settings that will restrict the queries that can be run against a large list. These settings can be configured for each Web application and will control the following:
     The number of results that can be returned in a user query. The default value is 5,000 items.
     The warning level for site administrators that their list is close to the threshold limit. This warning is displayed on the list settings page. The default value is 3,000 items.
     The number of query results that can be displayed for a site administrator. This allows site administrators to access a larger data set than other site users. The default value is 20,000 items.
     The maximum number of unique scopes in a list. The default value is 50,000 items.
     The number of lookup columns that each list can include. The default value is 6 lookup columns.
  7. These settings are configured for each Web application. They can be accessed through the General Settings option on the Web application ribbon.
  8. Allowing object model override will allow for a query to be programmatically written against a list where the query threshold is not applied.
  9. Enabling a daily time window for large queries will provide a way for administrators to configure a specific window of time where the query thresholds are not applied.
  10. A Windows PowerShell command that will restrict specific lists from being queried through the object model (this would cancel out the object model override mentioned above for a specific list instance).

Multi-tenancy and Hosting
  1. Microsoft SharePoint Server 2010 has the capability to isolate and separate data from different Web sites while sharing service application resources across these same sites. This capability is called multi-tenancy.
  2. Multi-tenancy of services creates a true hosting environment and makes it possible to share service resources across customers (tenants) while partitioning data based on site subscriptions.
  3. Site subscriptions group tenant data across all site collections owned by the tenant, and provide the ability to separate and group each tenant’s data in an otherwise shared environment.
  4. Site Subscriptions - Multi-tenancy relies on site subscriptions and subscription IDs. Site collections for each tenant are grouped together by site subscription based on a common subscription ID.
  5. The subscription ID is used to map features and services to tenants and also to partition service data according to tenant.
  6. All site collections for a single site subscription must reside in the same Web application.
  7. Multiple site subscriptions can be hosted in a single Web application. Multiple site subscriptions can share the same database.
  8. Administrators define which services are available and activated for each tenant. The subscription ID for a tenant is used to map the service to the site collections.
  9. Multiple tenants can share service data. For example, multiple branches of an organization can share profile data. In this case, the multiple branches share a data partition within the profile service.
  10. Service data can be partitioned for each tenant, ensuring that customer data is not exposed to other tenants. In this case, data for a single tenant is contained within a separate data partition for the service.

More - SharePoint 2010 Top 10 Features

Source - SharePoint 2010 Resources

No comments: