manual

31 www.microsoft.com/sharepoint
grabs events from ULS, the Windows Event Log, usage database, and SPME; and is
integrated with ULS.
Remote BLOB Storage
For farms with large storage needs Microsoft® SharePoint® Server 2010 has
implemented remote BLOB storage (RBS). With RBS, it is possible to have BLOBs from
the all_docs table and customized pages in the database stored in a location outside of
the database, such as on file system, allowing for a reduction in the amount of Microsoft
SQL Server™ database storage. To use RBS, a provider is necessary. The RBS provider
architecture is completely pluggable, meaning that third-party vendors can create and
sell their own RBS providers and deliver specific capabilities. For example, a third party
backup vendor could use an RBS provider as part of their backup and restore capability.
The RBS architecture provides another degree of freedom for the storage of content. Its
intention is to be used natively by SharePoint during the upgrade process and by third
party vendors that provide storage benefits as a service.
Performance Controls
Microsoft® SharePoint® Server 2010 provides two different performance controls that
can be configured to help increase server performance and protect server resources
during peak usage times: throttling and list controls. Throttling provides a way to
control server resources and is designed so that the server can be protected from
overload during peak business hours. 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.
Throttling
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. Requests that were generated prior to the server's
entering throttling mode will be completed. This will, in theory, keep users from losing