Microsoft Office Tutorials and References
In Depth Information
It is here the default settings for things such as time zone, quota, alerts, Recycle Bin, blog
API, browser file handling, maximum upload settings, and so on, are set per web
application. This page of settings was covered in detail in Chapter 10.
Something of particular interest concerning the Recycle Bin settings in General Settings that is
often overlooked is the percentage of space the second-stage Recycle Bin takes. When you create a
site collection quota, the deleted items sitting in the user Recycle Bin take up space in that quota.
However, if you delete items from the user Recycle Bin, they go to the second-stage, site-collection
Recycle Bin. Why would we encourage you to empty the user Recycle Bins in order to free up space
in the site collection quota? It’s because, in the General Settings page for a web application is the
second-stage Recycle Bin setting called Add A Certain Percentage Of Live Site Quota For Second
Stage Deleted Items. You can enter a certain percentage (50 percent is the default) indicating how
much in addition to the site quota the second-stage Recycle Bin can store before it maxes out and
older items are automatically removed. This setting is obviously per web application and affects
all site collections within it.
Resource Throttling Resource throttling is new with this version of SharePoint. Lists in
a site are all organized in one place in the content database. Previously, SharePoint had a
soft display limit of about 2,000 items. When a user went to the content page of a list with
2,000 or more items, it would lag horribly and, because of its location, would likely make
a lot of other lists lag for other users as well. This version of SharePoint is supposed to be
so good it can support lists with millions of items, yet throttling is set to some
surprisingly low numbers. I guess it is because SharePoint (or maybe the database engines on
the back end) can handle a large amount of data, but it still finds it challenging to query
nearly that number of things.
And, although it might be argued that this is bad design, SharePoint has tried to ix the
issue by allowing you to throttle the number of things a user can do—to help avoid (but
not ix) the choking and crashing that large lists or many page requests can cause. The
Resource Throttling box has a number of settings that relate to how SharePoint will fail
to return data if the user is trying to access a list too large or a site too busy. The settings
include several list view threshold settings, object model override, and daily time
window for large queries. For more details concerning these settings, see Chapter 10.
In Chapter 1 there were a bunch of software boundary tables that listed software limits,
boundaries, and thresholds. Thresholds were performance limits that were set in SharePoint at a default
level, but they could be changed administratively. These threshold settings for resource throttling
are an excellent example of the defaults that limit how many items a list view will display before
failing, unique permissions for a list, and HTTP request throttling (and monitoring). It is here that
you can increase (or decrease) the thresholds of these settings.
Search JabSto ::

Custom Search