Wednesday, November 21, 2012

SharePoint 2013 Boundaries and Limits Overview


 This tech-net article contains information to help you understand the tested performance and capacity limits of SharePoint Server 2013, and offers guidelines for how limits relate to acceptable performance. Use the information in this article to determine whether your planned deployment falls within acceptable performance and capacity limits, and to appropriately configure limits in your environment.

The test results and guidelines provided in this article apply to a single SharePoint Server 2013 farm. Adding servers to the installation might not increase the capacity limits of the objects that are listed in the tables in the Limits and boundaries section later in this topic. On the other hand, adding server computers increases the throughput of a server farm, which might be necessary to achieve acceptable performance with many objects. In some cases, the requirements for high numbers of objects in a solution might require more servers in the farm.

Note that there are many factors that can affect performance in a given environment, and each of these factors can affect performance in different areas. Some of the test results and recommendations in this article might be related to features or user operations that do not exist in your environment, and therefore do not apply to your solution. Only thorough testing can give you exact data related to your own environment.

Boundaries, thresholds and supported limits

In SharePoint Server 2013, there are certain limits that are by design and cannot be exceeded, and other limits that are set to default values that may be changed by the farm administrator. There are also certain limits that are not represented by a configurable value, such as the number of site collections per web application.
  • Boundaries are absolute limits that cannot be exceeded by design. It is important to understand these limits to ensure that you do not make incorrect assumptions when you design your farm.
    An example of a boundary is the 2 GB document size limit; you cannot configure SharePoint Server 2013 to store documents that are larger than 2 GB. This is a built-in absolute value, and cannot be exceeded by design.
  • Thresholds are those that have a default value that cannot be exceeded unless the value is modified. Thresholds can, in certain circumstances, be exceeded to accommodate variances in your farm design, but it is important to understand that doing this may affect the performance of the farm in addition to the effective value of other limits.
    The default value of certain thresholds can only be exceeded up to an absolute maximum value. A good example is the document size limit. By default, the default document size threshold is set to 50MB, but can be changed to support the maximum boundary of 2GB.
  • Supported limits define the tested value for a given parameter. The default values for these limits were defined by testing, and represent the known limitations of the product. Exceeding supported limits may cause unexpected results, significant decrease in performance, or other harmful effects.
    Some supported limits are configurable parameters that are set by default to the recommended value, while other supported limits relate to parameters that are not represented by a configurable value.
An example of a supported limit is the number of site collections per farm. The supported limit is the largest number of site collections per web application that met performance benchmarks during testing.

It is important to be aware that many of the limit values that are provided in this document represent a point in a curve that describes an increasing resource load and concomitant decrease in performance as the value increases. Therefore, exceeding certain limits, such as the number of site collections per web application, may only result in a fractional decrease in farm performance. However, in most cases, operating at or near an established limit is not a best practice, as acceptable performance and reliability targets are best achieved when a farm’s design provides for a reasonable balance of limits values.

Thresholds and supported limits guidelines are determined by performance. In other words, you can exceed the default values of the limits, but as you increase the limit value, farm performance and the effective value of other limits may be affected. Many limits in SharePoint Server 2013 can be changed, but it is important to understand how changing a given limit affects other parts of the farm.

How limits are established

In SharePoint Server 2013, thresholds and supported limits are established through testing and observation of farm behavior under increasing loads up to the point where farm services and operations reach their effective operational limits. Some farm services and components can support a higher load than others so that in some cases you must assign a limit value based on an average of several factors.

For example, observations of farm behavior under load when site collections are added indicate that certain features exhibit unacceptably high latency while other features are still operating within acceptable parameters. Therefore, the maximum value assigned to the number of site collections is not absolute, but is calculated based on an expected set of usage characteristics in which overall farm performance would be acceptable at the given limit under most circumstances.

Obviously, if some services are operating under parameters that are higher than those used for limits testing, the maximum effective limits of other services will be reduced. It is therefore important to execute rigorous capacity management and scale testing exercises for specific deployments in order to establish effective limits for that environment.

Note: We do not describe the hardware that was used to validate the limits in this document, because the limits were collected from multiple farms and environments.

The Pie Metaphor

In order to understand the relationship between hardware resources, load and performance, it’s important to have a way to visualize the factors involved and how they affect each other.
Consider the capacity of a farm as a pie, the size of which represents the aggregate of factors such as servers, hardware resources such as CPUs and RAM, storage capacity, disk IOPs, network bandwidth and latency. The size of the pie is therefore related to the overall resources of the farm; adding resources (such as farm servers) increases the size of the pie.

This pie is divided into slices that represent load from a variety of sources: user requests, search queries, operations against installed features, timer jobs and operating system overhead. Each of these sections must share available farm resources. If the size of one slice increases, the size of others must decrease proportionally. Since load on a farm is not static (user requests, for example, might only be significant during certain hours of the day), the relative size of the slices is constantly in flux. However, each slice must maintain a required minimum size to operate normally, and since the functions represented by each slice are interdependent, increasing the size of one slice may place more load on other slices in addition to reducing the resources available for them to consume.
Using this metaphor, the goal of the farm’s design is to make the pie large enough to accommodate the required size of each pie slice under peak load.

Now, consider a scenario where user requests increase by 100% over baseline. Let’s say that about half of the requests are search queries, and the other half editing lists and documents. This increased load squeezes the other pie slices, but some farm features must also work harder to compensate. The Search service has to process more queries, most of which are handled by the cache, but some queries are passed on to the database servers, increasing their load as well. If load on the database servers becomes too great, disk queue lengths will increase, which in turn increases the latency of all other requests.

Limits and boundaries

This section lists the objects that can be a part of a solution and provides guidelines for acceptable performance for each kind of object. Acceptable performance means that the system as tested can support that number of objects, but that the number cannot be exceeded without some decrease in performance or a reduction in the value of related limits. Objects are listed both by scope and by feature. Limits data is provided, together with notes that describe the conditions under which the limit is obtained and links to additional information where available.
Use the guidelines in this article to review your overall solution plans. If your solution plans exceed the recommended guidelines for one or more objects, take one or more of the following actions:
  • Evaluate the solution to ensure that compensations are made in other areas.
  • Flag these areas for testing and monitoring as you build your deployment.
  • Redesign or partition the solution to ensure that you do not exceed capacity guidelines.

Limits by hierarchy

This section provides limits sorted by the logical hierarchy of a SharePoint Server 2013 farm.

Web application limits

The following table lists the recommended guidelines for web applications.
Limit Maximum value Limit type Notes
Web application20 per farmSupportedWe recommended limiting the number of web applications as much as possible. Create additional host named site collections where possible instead of adding web applications.
Zone5 per web applicationBoundaryThe number of zones defined for a farm is hard-coded to 5. Zones include Default, Intranet, Extranet, Internet, and custom.
Managed path20 per web applicationSupportedManaged paths are cached on the web server, and CPU resources are used to process incoming requests against the managed path list.
Exceeding 20 managed paths per web application adds more load to the web server for each request.
If you plan to exceed twenty managed paths in a given web application, we recommend that you test for acceptable system performance.
Solution cache size300 MB per web applicationThresholdThe solution cache allows the InfoPath Forms service to hold solutions in cache in order to speed up retrieval of the solutions. If the cache size is exceeded, solutions are retrieved from disk, which may slow down response times. You can configure the size of the solution cache by using the Windows PowerShell cmdlet Set-SPInfoPathFormsService. For more information, see Set-SPInfoPathFormsService.

Web server and application server limits

The following table lists the recommended guidelines for web servers on the farm.
Limit Maximum value Limit type Notes
Application pools10 per web serverSupportedThe maximum number is determined by hardware capabilities.
This limit is dependent largely upon:
  • The amount of memory allocated to the web servers
  • The workload that the farm is serving, that is, the user base and the usage characteristics (a single highly active application pool can utilize 10 GB or more)

Content database limits

The following table lists the recommended guidelines for content databases.
Limit Maximum value Limit type Notes
Number of content databases500 per farmSupportedThe maximum number of content databases per farm is 500. With 500 content databases per web application, end user operations such as opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use Windows PowerShell to manage the web application when a large number of content databases are present, because the management interface might become slow and difficult to navigate.
Content database size (general usage scenarios)200 GB per content databaseSupportedWe strongly recommended limiting the size of content databases to 200 GB, except when the circumstances in the following rows in this table apply.
If you are using Remote BLOB Storage (RBS), the total volume of remote BLOB storage and metadata in the content database must not exceed this limit.
Content database size (all usage scenarios)4 TB per content databaseSupportedContent databases of up to 4 TB are supported when the following requirements are met:
  • Disk sub-system performance of 0.25 IOPs per GB. 2 IIOPs per GB is recommended for optimal performance.
  • You must have developed plans for high availability, disaster recovery, future capacity, and performance testing.
You should also carefully consider the following factors:
  • Requirements for backup and restore may not be met by the native SharePoint Server 2013 backup for content databases larger than 200 GB. It is recommended to evaluate and test SharePoint Server 2013 backup and alternative backup solutions to determine the best solution for your specific environment.
  • It is strongly recommended to have proactive skilled administrator management of the SharePoint Server 2013 and SQL Server installations.
  • The complexity of customizations and configurations on SharePoint Server 2013 may necessitate refactoring (or splitting) of data into multiple content databases. Seek advice from a skilled professional architect and perform testing to determine the optimum content database size for your implementation. Examples of complexity may include custom code deployments, use of more than 20 columns in property promotion, or features listed as not to be used in the over 4 TB section below.
  • Refactoring of site collections allows for scale out of a SharePoint Server 2013 implementation across multiple content databases. This permits SharePoint Server 2013 implementations to scale indefinitely. This refactoring will be easier and faster when content databases are less than 200 GB.
  • It is suggested that for ease of backup and restore that individual site collections within a content database be limited to 100 GB. For more information, see Site collection limits.
ImportantImportant:
Content databases of over 4 TB, except for use in document archive scenarios (described in the row below), are not recommended. Upgrading of site collections within these content databases is likely to be very difficult and time consuming.
It is strongly recommended that you scale out across multiple content databases, rather than exceed 4 TB of data in a single content database.
Content database size (document archive scenario)No explicit content database limitSupportedContent databases with no explicit size limit for use in document archive scenarios are supported when the following requirements are met:
  • You must meet all requirements from the “Content database size (all usage scenarios)” limit earlier in this table, and you should ensure that you have carefully considered all the factors discussed in the Notes field of that limit.
  • SharePoint Server 2013 sites must be based on Document Center or Records Center site templates.
  • Less than 5% of the content in the content database is accessed each month on average, and less than 1% of content is modified or written each month on average.
  • Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint Server 2013 objects in the content database.
    noteNote:
    Document archive content databases can be configured to accept documents from Content Routing workflows.
For more information about large-scale document repositories, see Estimate Performance and Capacity Requirements for Large Scale Document Repositories (http://technet.microsoft.com/en-us/library/ff608068.aspx), and the Typical large-scale content management scenarios section of the article Plan enterprise content storage in SharePoint 2013.
Content database items60 million items including documents and list itemsSupportedThe largest number of items per content database that has been tested on SharePoint Server 2013 is 60 million items, including documents and list items. If you plan to store more than 60 million items in SharePoint Server 2013, you must deploy multiple content databases.
Site collections per content database10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone)SupportedWe strongly recommended limiting the number of site collections in a content database to 5,000. However, up to 10,000 site collections in a database are supported. Note that in a content database with up to 10,000 total site collections, a maximum of 2,500 of these can be non-Personal site collections. It is possible to support 10,000 Personal site collections if they are the only site collections within the content database.
These limits relate to speed of upgrade. The larger the number of site collections in a database, the slower the upgrade with respect to both database upgrade and site collection upgrades.
The limit on the number of site collections in a database is subordinate to the limit on the size of a content database that has more than one site collection. Therefore, as the number of site collections in a database increases, the average size of the site collections it contains must decrease.
Exceeding the 5,000 site collection limit puts you at risk of longer downtimes during upgrades. If you plan to exceed 5,000 site collections, we recommend that you have a clear upgrade strategy to address outage length and operations impact, and obtain additional hardware to speed up the software updates and upgrades that affect databases.
To set the warning and maximum levels for the number of sites in a content database, use the Windows PowerShell cmdlet Set-SPContentDatabase with the -WarningSiteCount parameter. For more information, see Set-SPContentDatabase.
Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS) Time to first byte of any response from the NAS cannot exceed 20 milliseconds

BoundaryWhen SharePoint Server 2013 is configured to use RBS, and the BLOBs reside on NAS storage, consider the following boundary.
From the time that SharePoint Server 2013 requests a BLOB, until it receives the first byte from the NAS, no more than 20 milliseconds can pass.

Site collection limits

The following table lists the recommended guidelines for site collections.
Limit Maximum value Limit type Notes
Site collections per farm750,000 (500,000 Personal Sites and 250,000 other sites per farm)SupportedThe maximum recommended number of site collections per farm is 500,000 Personal Sites plus 250,000 for all other site templates. The Sites can all reside on one web application, or can be distributed across multiple web applications.
Note that this limit is affected by other factors that might reduce the effective number of site collections that can be supported by a given content database. Care must be exercised to avoid exceeding supported limits when a container object, such as a content database, contains a large number of other objects. For example, if a farm contains a smaller total number of content databases, each of which contains a large number of site collections, farm performance might be adversely affected long before the supported limit for the number of site collections is reached.
For example, Farm A contains a web application that has 200 content databases, a supported configuration. If each of these content databases contains 1,000 site collections, the total number of site collections in the web application will be 200,000, which falls within supported limits. However, if each content database contains 10,000 site collections, even though this number is supported for a content database, the total number of site collections in the farm will be 2,000,000, which exceeds the limit for the number of site collections per web application.
Memory usage on the web servers should be monitored, as memory usage is dependent on usage patterns and how many sites are being accessed in given timeframe. Similarly, the crawl targets might also exhibit memory pressure, and if so the application pool should be configured to recycle before available memory on any web server drops to less than 2 GB.
Web site250,000 per site collectionSupportedThe maximum recommended number of sites and subsites is 250,000 sites.
You can create a very large total number of web sites by nesting subsites. For example, in a shallow hierarchy with 100 sites, each with 1,000 subsites, you would have a total of 100,000 web sites. Or a deep hierarchy with 100 sites, each with 10 subsite levels would also contain a total of 100,000 web sites.
Note: Deleting or creating a site or subsite can significantly affect a site’s availability. Access to the site and subsites will be limited while the site is being deleted. Attempting to create many subsites at the same time may also fail.
Site collection sizeMaximum size of the content databaseSupportedA site collection can be as large as the content database size limit for the applicable usage scenario. For more information about the different content database size limits for specific usage scenarios, see the Content database limits table in this article.
In general, we strongly recommend limiting the size of site collections to 100 GB for the following reasons:
  • Certain site collection actions, such as site collection backup/restore or the Windows PowerShell cmdlet Move-SPSite, cause large SQL Server operations which can affect performance or fail if other site collections are active in the same database. For more information, see Move-SPSite.
  • SharePoint site collection backup and restore is only supported for a maximum site collection size of 100 GB. For larger site collections, the complete content database must be backed up. If multiple site collections larger than 100 GB are contained in a single content database, backup and restore operations can take a long time and are at risk of failure.
Number of device channels per publishing site collection10BoundaryThe maximum allowed number of device channels per publishing site collection is 10.

List and library limits

The following table lists the recommended guidelines for lists and libraries. For more information, see Designing large lists and maximizing list performance (SharePoint Server 2010).
Limit Maximum value Limit type Notes
List row size8,000 bytes per rowBoundaryEach list or library item can only occupy 8,000 bytes in total in the database. 256 bytes are reserved for built-in columns, which leaves 7,744 bytes for end-user columns. For details on how much space each kind of field consumes, see Column limits.
File size2 GBBoundaryThe default maximum file size is 50 MB. This can be increased up to 2 GB. However a large volume of very large files can affect farm performance.
Documents30,000,000 per librarySupportedYou can create very large document libraries by nesting folders, or using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.
Major versions400,000SupportedIf you exceed this limit, basic file operations—such as file open or save, delete, and viewing the version history— may not succeed.
Minor versions511BoundaryThe maximum number of minor file versions is 511. This limit cannot be exceeded.
Items30,000,000 per listSupportedYou can create very large lists using standard views, site hierarchies, and metadata navigation. This value may vary depending on the number of columns in the list and the usage of the list.
Rows size limit6 table rows internal to the database used for a list or library itemSupportedSpecifies the maximum number of table rows internal to the database that can be used for a list or library item. To accommodate wide lists with many columns, each item may be wrapped over several internal table rows, up to six rows by default. This is configurable by farm administrators through the object model only. The object model method is SPWebApplication.MaxListItemRowStorage.
Bulk operations100 items per bulk operationBoundaryThe user interface allows a maximum of 100 items to be selected for bulk operations.
List view lookup threshold8 join operations per queryThresholdSpecifies the maximum number of joins allowed per query, such as those based on lookup, person/group, or workflow status columns. If the query uses more than eight joins, the operation is blocked. This does not apply to single item operations. When using the maximal view via the object model (by not specifying any view fields), SharePoint will return up to the first eight lookups.
List view threshold5,000ThresholdSpecifies the maximum number of list or library items that a database operation, such as a query, can process at the same time outside the daily time window set by the administrator during which queries are unrestricted.
List view threshold for auditors and administrators20,000ThresholdSpecifies the maximum number of list or library items that a database operation, such as a query, can process at the same time when they are performed by an auditor or administrator with appropriate permissions. This setting works with Allow Object Model Override.
Subsite2,000 per site viewThresholdThe interface for enumerating subsites of a given web site does not perform well as the number of subsites surpasses 2,000. Similarly, the All Site Content page and the Tree View Control performance will decrease significantly as the number of subsites grows.
Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files 10 concurrent editors per documentThresholdRecommended maximum number of concurrent editors is 10. The boundary is 99.
If there are 99 co-authors who have a single document opened for concurrent editing, each successive user sees a "File in use" error, and can only open a read-only copy.
More than 10 co-editors will lead to a gradually degraded user experience with more conflicts, and users might have to go through more iterations to successfully upload their changes to the server.
Security scope1,000 per listThresholdThe maximum number of unique security scopes set for a list should not exceed 1,000.
A scope is the security boundary for a securable object and any of its children that do not have a separate security boundary defined. A scope contains an Access Control List (ACL), but unlike NTFS ACLs, a scope can include security principals that are specific to SharePoint Server 2013. The members of an ACL for a scope can include Windows users, user accounts other than Windows users (such as forms-based accounts), Active Directory groups, or SharePoint groups.

Column limits

SharePoint Server 2013 data is stored in SQL Server tables. To allow for the maximum number of possible columns in a SharePoint list, SharePoint Server 2013 will create several rows in the database when data will not fit on a single row. This is called row wrapping.

Each time that a row is wrapped in SQL Server, an additional query load is put on the server when that item is queried because a SQL join must be included in the query. To prevent too much load, by default a maximum of six SQL Server rows are allowed for a SharePoint item. This limit leads to a particular limitation on the number of columns of each type that can be included in a SharePoint list.

The following table describes the limits for each column type.

The row wrapping parameter can be increased beyond six, but this may result in too much load on the server. Performance testing is recommended before exceeding this limit. For more information, see Designing large lists and maximizing list performance (SharePoint Server 2010).
Each column type has a size value listed in bytes. The sum of all columns in a SharePoint list cannot exceed 8,000 bytes. Depending on column usage, users can reach the 8,000 byte limitation before reaching the six-row row wrapping limitation.
Limit Maximum value Limit type Size per column Notes
Single line of text276Threshold28 bytesSQL Server row wrapping occurs after each 64 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 384 Single line of text columns per SharePoint list (6 * 64 = 384). However, because the limit per SharePoint list item is 8,000 bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual limit is 276 Single line of text columns.
Multiple Lines of Text192Threshold28 bytesSQL Server row wrapping occurs after each 32 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 192 Multiple lines of text columns per SharePoint list (6 * 32 = 192).
Choice276Threshold28 bytesSQL Server row wrapping occurs after each 64 columns in a SharePoint list. The default row wrapping value of 6 allows for a maximum of 384 Choice columns per SharePoint list (6 * 64 = 384); ); however because the limit per SharePoint list item is 8,000 bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual limit should be 276 Choice columns.
Number 72Threshold12 bytesSQL Server row wrapping occurs after each 12 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 72 Number columns per SharePoint list (6 * 12 = 72).
Currency72Threshold12 bytesSQL Server row wrapping occurs after each 12 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 72 Currency columns per SharePoint list (6 * 12 = 72).
Date and Time48Threshold12 bytesSQL Server row wrapping occurs after each eight columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 48 Date and Time columns per SharePoint list (6 * 8 = 48).
Lookup 96Threshold4 bytesSQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 single value Lookup columns per SharePoint list (6 * 16 = 96).
Yes / No96Threshold5 bytesSQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 Yes / No columns per SharePoint list (6 * 16 = 96).
Person or group96Threshold4 bytesSQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 Person or Group columns per SharePoint list (6 * 16 = 96).
Hyperlink or picture138Threshold56 bytesSQL Server row wrapping occurs after each 32 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 192 Hyperlink or Picture columns per SharePoint list (6 * 32 = 192) ); however because the limit per SharePoint list item is 8,000 bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual limit should be 138 Hyperlink or Picture columns.
Calculated48Threshold28 bytesSQL Server row wrapping occurs after each eight columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 48 Calculated columns per SharePoint list (6 * 8 = 48).
GUID6Threshold20 bytesSQL Server row wrapping occurs after each column in a SharePoint list. The default row wrapping value of six allows for a maximum of 6 GUID columns per SharePoint list (6 * 1 = 6).
Int96Threshold4 bytesSQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 Int columns per SharePoint list (6 * 16 = 96).
Managed metadata94Threshold40 bytes for the first, 32 bytes for each subsequentThe first Managed Metadata field added to a list is allocated four columns:
  • A lookup field for the actual tag
  • A hidden text field for the string value
  • A lookup field for the catch all
  • A lookup field for spillover of the catch all
Each subsequent Managed Metadata field added to a list adds two more columns:
  • A lookup field for the actual tag
  • A hidden text field for the string value
The maximum number of columns of Managed Metadata is calculated as (14 + (16 * (n-1))) where n is the row mapping value (default of 6).

External Data columns have the concept of a primary column and secondary columns. When you add an external data column, you can select some secondary fields of the external content type that you want to be added to the list. For example, given an External Content Type “Customer” which has fields like “ID”, “Name”, “Country”, and “Description”, when you add an External Data column of type “Customer” to a list, you can add secondary fields to show the “ID”, “Name” and “Description” of the Customer. Overall these are the columns that get added:
  • Primary column: A text field.
  • Hidden Id column: A multi-line text field.
  • Secondary columns: Each secondary column is a text/number/Boolean/multi-line text that is based on the data type of the secondary column as defined in the Business Data Catalog model. For example, ID might be mapped to a Number column; Name might be mapped to a Single line of text column; Description might be mapped to a Multiple lines of text column.

Page limits

The following table lists the recommended guidelines for pages.
Limit Maximum value Limit type Notes
Web parts25 per wiki or Web Part page ThresholdThis figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected.

Security limits

Limit Maximum value Limit type Notes
Number of SharePoint groups a user can belong to5,000SupportedThis is not a hard limit but it is consistent with Active Directory guidelines. There are several things that affect this number:
  • The size of the user token
  • The groups cache: SharePoint Server 2013 has a table that caches the number of groups a user belongs to as soon as those groups are used in access control lists (ACLs).
  • The security check time: as the number of groups that a user is a member of increases, the time that is required for the access check increases also.
Users in a site collection2 million per site collectionSupportedYou can add millions of people to your web site by using Microsoft Windows security groups to manage security instead of using individual users.
This limit is based on manageability and ease of navigation in the user interface.
When you have many entries (security groups of users) in the site collection (more than one thousand), you should use Windows PowerShell to manage users instead of the UI. This will provide a better management experience.
Active Directory Principles/Users in a SharePoint group5,000 per SharePoint group SupportedSharePoint Server 2013 enables you to add users or Active Directory groups to a SharePoint group.
Having up to 5,000 users (or Active Directory groups or users) in a SharePoint group provides acceptable performance.
The activities most affected by this limit are as follows:
  • Fetching users to validate permissions. This operation takes incrementally longer with growth in number of users in a group.
  • Rendering the membership of the view. This operation will always require time.
SharePoint groups10,000 per site collectionSupportedAbove 10,000 groups, the time to execute operations is increased significantly. This is especially true of adding a user to an existing group, creating a new group, and rendering group views.
Security principal: size of the Security Scope5,000 per Access Control List (ACL)SupportedThe size of the scope affects the data that is used for a security check calculation. This calculation occurs every time that the scope changes. There is no hard limit, but the bigger the scope, the longer the calculation takes.

Limits by feature

This section lists limits sorted by feature.

Search limits

The following table lists the recommended guidelines for Search.
noteNote:
Limits for Search have changed significantly as the feature has been updated. For more information, see Plan search in SharePoint Server 2013.
Limit Maximum value Limit type Notes
Search service applications20 per farmSupportedMultiple Search service applications can be deployed on the same farm, because you can assign search components and databases to separate servers. This limit is lower than the limit for the total number of service applications in a farm.
Crawl databases 5 crawl databases per search service applicationBoundaryThe crawl database stores the crawl data (time/status, etc.) about all items that have been crawled. The supported limit is 5 crawl databases per SharePoint Search service application.
Crawl components2 per search service applicationThreshold
Index components60 per Search service applicationSupportedThe maximum number of index components that can be used is achieved by multiplying the index partitions limit with the index replicas limit.
Index partitions20 per search service applicationSupportedAn index partition holds a subset of the Search service application index. Increasing the number of index partitions results in each partition holding a smaller subset of the index, reducing the RAM and disk space that is needed on the servers hosting the index components.
Index replicas3 per index partitionSupportedEach index partition can have a set of replicas. If you increase the number of index replicas this will have a positive effect on the query performance and it provides better fault tolerance. However, if you add too many replicas to your index partition, this can have a negative effect on indexing.
Indexed items100 million per search service application; 10 million per index partitionSupportedEach index partition contains a subset of the entire search index. If the number of indexed items is high in relation to the amount of memory the server has, this will affect the query response time negatively.
Crawl log entries100 million per search applicationSupportedThis is the number of individual log entries in the crawl log. It will follow the "Indexed items" limit.
Property databases10 per search service application;128 totalThresholdThe property database stores the metadata for items in each index partition associated with it. An index partition can only be associated with one property store. The recommended limit is 10 property databases per search service application. The boundary for index partitions is 128.
Link databaseTwo per Search service applicationThresholdEach link database can contain up to 50 million items.
Query processing components1 per server computerThresholdSharePoint only supports one query processing component per physical machine or virtual machine.
Content processing componentsOne per server computerSupportedThe topology supports scaling out the number of Content processing components.
Although a specific physical host or virtual machine does support multiple Content processing components, you achieve better usage of the CPU capacity by using one Content processing component. The reason is that a built-in mechanism maximizes CPU usage by adjusting the number of feeding sessions in accordance with available CPU cores. Multiple feeding sessions allow the Content processing component to process incoming documents in parallel. This mechanism assumes a single Content processing component per host.
If the number of physical cores on the host equals N, then the Content processing component will have N*K feeding sessions. K is a constant coefficient with the initial value 3. A 4-core server will have 12 feeding sessions, which means that the Content processing component can process 12 documents in parallel. You can change the value of K by setting the NumberOfCssFeedersPerCPUForRegularCrawl property of the Search Service Application. SharePoint 2013 limits the value of N upwards to 12, even if a server has more than 12 physical cores. Therefore a 16-core server will have N*K = 12 * 3 = 36 feeding sessions.
In the case that there still is idle CPU time, consider increasing the K coefficient instead of adding an extra Content processing component. If you increase the K coefficient, you must ensure that the host has sufficient available memory.
Scope rules100 scope rules per scope; 600 total per search service applicationThresholdExceeding this limit will reduce crawl freshness, and delay potential results from scoped queries.
Scopes200 site scopes and 200 shared scopes per search service applicationThresholdExceeding this limit may reduce crawl efficiency and, if the scopes are added to the display group, affect end-user browser latency. Also, display of the scopes in the search administration interface degrades as the number of scopes passes the recommended limit.
Display groups25 per siteThresholdDisplay groups are used for a grouped display of scopes through the user interface. Exceeding this limit starts degrading the scope experience in the search administration interface.
Alerts100,000 per search applicationSupportedThis is the limit for a Search service application with a mix of end user queries (75%) and alert queries (25%). The limit for a Search service application with only alert queries is 400,000 alerts. These limits are based on a system with five queries per second (QPS).
Content sources50 per search service applicationThresholdThe recommended limit of 50 can be exceeded up to the boundary of 500 per search service application. However, fewer start addresses should be used, and the concurrent crawl limit must be followed.
Start addresses100 per content sourceSupported
Concurrent crawls20 per search applicationThresholdThis is the number of crawls underway at the same time. Exceeding this number may cause the overall crawl rate to decrease.
Crawled properties500,000 per search applicationSupportedThe contents and metadata of the items that you crawl are represented as crawled properties. You can map these crawled properties to managed properties. When the number of crawled properties exceeds this supported limit, indexing speed will be reduced.
Crawl impact ruleno limitSupported
Crawl rulesno limitSupported
Managed properties50,000 per search service applicationSupportedSearch uses managed propertied in queries. Crawled properties are mapped to managed properties. When you exceed the supported limit for managed properties, this reduces indexing speed.
Values per managed property100SupportedA managed property can have multiple values of the same type. This is the supported number of values per managed multi-valued managed property per document. Exceeding this limit may have a negative effect on query performance, index disk size and/or memory usage.
Indexed managed property size512 KB per searchable/queryable managed propertyThresholdThis is the default limit for the size of a searchable or queryable managed property. If you increase this limit, you will enable indexing of more data per managed property. Indexing more data per managed property uses more disk space and increases the overall load on the system. You can configure this limit by using Windows PowerShell cmdlets and the schema object model to set the MP.MaxCharactersInPropertyStoreIndex attribute.
Managed property mappings100 per managed propertySupportedCrawled properties can be mapped to managed properties. Exceeding this limit may decrease crawl speed and query performance.
Retrievable managed property size16 KB per managed propertyThresholdThis is the default maximum limit for the size of a retrievable managed property. Increasing this limit will enable indexing of more data per managed property. It will also enable retrieval of more data per managed property with the search results. Indexing and retrieving more data per managed property increases the overall load on the system and uses more disk space. You can configure this limit per managed property by using Windows PowerShell cmdlets and the schema object model to set the P.MaxCharactersInPropertyStoreForRetrieval attribute.
Sortable and refinable managed property size16 KB per managed propertyBoundaryThis is the default maximum limit for the size of a sortable and refinable managed property. Increasing this limit will enable indexing of more data per managed property. This uses more disk space and increases the overall load on the system. You can configure this limit per managed property by using Windows PowerShell cmdlets and the schema object model to set the MP.MaxCharactersInPropertyStoreForRetrieval attribute.
URL removals100 removals per operationSupportedThis is the maximum recommended number of URLs that should be removed from the system in one operation.
Authoritative pages1 top level and minimal second and third level pages per search service applicationThresholdThe recommended limit is one top-level authoritative page, and as few second -and third-level pages as possible to achieve the desired relevance.
The boundary is 200 per relevance level per search application, but adding additional pages may not achieve the desired relevance. Add the key site to the first relevance level. Add more key sites at either second or third relevance levels, one at a time, and evaluate relevance after each addition to ensure that the desired relevance effect is achieved.
Keywords200 per site collectionSupportedThe recommended limit can be exceeded up to the maximum (ASP.NET-imposed) limit of 5,000 per site collection given five Best Bets per keyword. If you exceed this limit, display of keywords on the site administration user interface will degrade. The ASP.NET-imposed limit can be modified by editing the Web.Config and Client.config files (MaxItemsInObjectGraph).
Metadata properties recognized10,000 per item crawledBoundaryThis is the number of metadata properties that can be determined and potentially mapped or used for queries when an item is crawled.
Analytics processing components6 per Search service applicationThreshold
Analytics reporting databaseFour per Search service applicationThresholdAdd an analytics reporting database when the size of any of the deployed analytics databases reaches 250 GB. This way repartitioning is as balanced as possible.
Maximum eDiscovery KeywordQuery text length16 KBSupportedThe Keyword Query Language is a query language for building search queries. This is the default limit for the maximum text length of an eDiscovery keyword query.
Maximum KeywordQuery text length4 KBSupportedThe Keyword Query Language is a query language for building search queries. This is the default limit for the maximum text length of a keyword query.
Maximum length of eDiscovery KeywordQuery text at Search service application level20 KBBoundaryThe Keyword Query Language is a query language for building search queries. This is the maximum boundary for the text length of an eDiscovery keyword query. This boundary is valid at the Search service application level.
Maximum length of KeywordQuery text at Search service application level20 KBBoundaryThe Keyword Query Language is a query language for building search queries. This is the maximum boundary for the text length of a keyword query. This boundary is valid at the Search service application level.
Maximum size of documents pulled down by crawler64 MB (3 MB for Excel documents)Boundary
Navigable results from search100,000 per query request per Search service applicationSupportedThis is the limit for how many hits that a query requests. Increasing this limit will affect the query performance negatively.
Number of entries in a custom entity extraction dictionary1 millionSupportedThis is the tested limit.
Number of entries in a custom search dictionary5,000 terms per tenantBoundaryThis limits the number of terms allowed for inclusions and exclusions dictionaries for query spelling correction and company extraction.
Number of entries in a thesaurus1 millionSupportedThis is the tested limit.
Ranking models1,000 per tenantBoundaryApproaching this limit can have negative effect on the overall system performance.
Results removalNo limitSupported
Term size300 charactersBoundaryTerms that are longer than this boundary will be split into two or more terms where no term has more than 300 characters. For example, a 612-character term will be split into two 300-character terms and one 12-character term. Only the first 1000 characters of a term are considered for splitting, any remaining characters are ignored.
Unique terms in the index2^31 (>2 billion terms)BoundaryThis is the maximum boundary for the number of unique terms that can exist in the index of a Search service application.
Unique contexts used for ranking15 unique contexts per rank modelBoundaryThis is the maximum boundary for the number of unique contexts per rank model.
User defined full text indexes10BoundaryThis is the maximum boundary for the number of full text indexes.

User Profile Service limits

The following table lists the recommended guidelines for User Profile Service.
Limit Maximum value Limit type Notes
User profiles2,000,000 per service applicationSupportedA user profile service application can support up to 2 million user profiles with full social features functionality. This number represents the number of profiles that can be imported into the people profile store from a directory service, and also the number of profiles a user profile service application can support without leading to performance decreases in social features.
Social tags, notes and ratings500,000,000 per social databaseSupportedUp to 500 million total social tags, notes and ratings are supported in a social database without significant decreases in performance. However, database maintenance operations such as backup and restore may show decreased performance at that point.

Content deployment limits

The following table lists the recommended guidelines for content deployment.
Limit Maximum value Limit type Notes
Content deployment jobs running on different paths20SupportedFor concurrently running jobs on paths that are connected to site collections in the same source content database, there is an increased risk of deadlocks on the database. For jobs that must run concurrently, we recommend that you move the site collections into different source content databases.
noteNote:
Concurrent running jobs on the same path are not possible.
If you are using SQL Server snapshots for content deployment, each path creates a snapshot. This increases the I/O requirements for the source database.
For more information, see About deployment paths and jobs.

Blog limits

The following table lists the recommended guidelines for blogs.
Limit Maximum value Limit type Notes
Blog posts5,000 per siteSupportedThe maximum number of blog posts is 5,000 per site.
Comments1,000 per postSupportedThe maximum number of comments is 1,000 per post.

Business Connectivity Services limits

The following table lists the recommended guidelines for Business Connectivity Services.
Limit Maximum value Limit type Notes
ECT (in-memory)5,000 per web server (per tenant)BoundaryTotal number of external content type (ECT) definitions loaded in memory at a given point in time on a web server.
External system connections500 per web serverBoundaryNumber of active/open external system connections at a given point in time. The default maximum value is 200; the boundary is 500. This limit is enforced at the web server scope, regardless of the kind of external system (for example, database, .NET assembly, and so on) The default maximum is used to restrict the number of connections. An application can specify a larger limit via execution context; the boundary enforces the maximum even for applications that do not respect the default.
Database items returned per request2,000 per database connectorThresholdNumber of items per request the database connector can return.
The default maximum of 2,000 is used by the database connector to restrict the number of result that can be returned per page. The application can specify a larger limit via execution context; the Absolute Max enforces the maximum even for applications that do not respect the default. The boundary for this limit is 1,000,000.
Response latency600 secondsThresholdTimeout used by the external data connector per request. The default value is 180 seconds, but applications can be configured to specify a larger value up to the maximum of 600 seconds.
Service response size150,000,000 bytesThresholdThe upper volume of data per request the external data connector can return. The default value is 3,000,000 bytes, but applications can be configured to specify a larger value up to the maximum of 150,000,000 bytes.
Filter Descriptor (in-store)200 per ECT methodBoundaryThe maximum number of Filter Descriptors per ECT method is 200.
ECT Identifier (in-store)20 per ECTBoundaryThe maximum number of identifiers per ECT is 20.
Database Item1,000,000 per requestThresholdThe default maximum number of items per request the database connector can return is 2,000, and the absolute maximum is 1,000,000.
The default max is used by the database connector to restrict the number of results that can be returned per page. The application can specify a larger limit via execution context; the absolute max enforces the allowed maximum even for applications that do not respect the default such as indexing.

Workflow limits

The following table lists the recommended guidelines for workflow.
Limit Maximum value Limit type Notes
Workflow postpone threshold15Threshold15 is the maximum number of workflows allowed to be executing against a content database at the same time, excluding instances that are running in the timer service. When this threshold is reached, new requests to activate workflows will be queued to be run by the workflow timer service later. As non-timer execution is completed, new requests will count against this threshold. This is limit can be configured by using the Set-SPFarmConfig Windows PowerShell cmdlet. For more information, see Set-SPFarmConfig.
Note: This limit does not refer to the total number of workflow instances that can be in progress. Instead, it is the number of instances that are being processed. Increasing this limit increases the throughput of starting and completing workflow tasks but also increases load against the content database and system resources.
Workflow timer batch size100ThresholdThe number of events that each run of the workflow timer job will collect and deliver to workflows. It is configurable by using Windows PowerShell. To allow for additional events, you can run additional instances of the SharePoint Foundation Workflow Timer Service.
Workflow associations100 per listSupportedExceeding this limit will degrade browser performance due to the large volume of data that is loaded for more than 100 associations and their status columns.
List items or documents that can be bulk created or uploaded to start workflow instances5,000 itemsSupportedTesting has verified that all workflow activation events are processed for an on-item-creation workflow association when up to 5,000 items are created in a single bulk upload. Exceeding this limit could cause workflow initiation to time out.
Published workflow definitions per web site1,000 per web siteSupportedThe maximum supported number of published workflow definitions per web site is 1,000.
Total workflow associations per site1,799 per siteBoundaryThe Service Bus supports a maximum of 1,799 subscriptions per scope. This maximum value includes the sum of both published and unpublished associations.
Maximum workflow definition (xaml) size5,120 KBBoundaryAttempts to publish xaml files that exceed the size limit will fail.
Maximum depth of a workflow sub-step in xaml (workflow complexity)121 levelsBoundaryThere is a hard limit of 125 for node depth in xaml. The maximum value of 121 levels accounts for the default activities (stage, sequence, etc.) that SharePoint Designer inserts automatically.
Workflow instance activations per second per web server6 per secondThresholdTesting has confirmed that a SharePoint web server can activate a maximum of 6 workflow instances per second. This number is cumulative, and therefore scales with the number of web servers in the farm. For example, 2 web servers can activate 12 workflow instances per second, and 3 web servers can activate 18.
Rest calls from SharePoint workflow per second per web server60 per secondSupportedTesting has confirmed that a SharePoint web server can effectively process up to 60 rest calls per second from SharePoint workflow.  If this level of volume will be exceeded, we recommend that an additional load-balanced web server be added to the SharePoint farm.In testing, 120 rest calls per second against a single web server resulted in sustained 90-100% CPU utilization. Adding a second web server reduced CPU utilization to 30-40% on both servers. Adding a third web server enabled processing of 180 calls per second, with 30-40% CPU utilization on all three servers, and so on. The servers used for this test were Hyper-V virtual machines with 16 core processor and 24 GBs RAM each.
Workflow variable value size256 KBBoundaryThe maximum amount of data that can be stored in a single workflow variable is 256 KB. Exceeding this limit will cause the workflow instance to terminate.
Maximum list size for workflow lookups to non-indexed fields5,000 items per list viewThresholdThis limit is a result of the maximum view size limit. When this limit is exceeded, workflow lookups to non-indexed fields will fail for non-administrative users. At this threshold, an index must be created for the field, in order for workflows to be able to successfully perform lookups against the field.
Maximum list size for auto-start workflow associations10 million items per listSupportedTesting has confirmed that the performance of auto-start workflow associations is not affected when list size grows to 1 million items.Because response time doesn't change as list size scales, the effective limit is the same as the maximum number of items in a non-workflow list.

Managed Metadata term store (database) limits

The following table lists the recommended guidelines for managed metadata term stores.
Limit Maximum value Limit type Notes
Maximum number of levels of nested terms in a term store7SupportedTerms in a term set can be represented hierarchically.  A term set can have up to seven levels of terms (a parent term, and six levels of nesting below it.)
Maximum number of term sets in a term store1,000SupportedYou can have up to 1,000 term sets in a term store.
Maximum number of terms in a term set30,000Supported30,000 is the maximum number of terms in a term set.
noteNote:
Additional labels for the same term, such as synonyms and translations, do not count as separate terms.
Total number of items in a term store1,000,000SupportedAn item is either a term or a term set. The sum of the number of terms and term sets cannot exceed 1,000,000. Additional labels for the same term, such as synonyms and translations, do not count as separate terms.
noteNote:
You cannot have both the maximum number of term sets and the maximum number of terms simultaneously in a term store.
Number of Variation Labels209 per term storeSupportedThe maximum number of Variation Labels per term store is 209.

Visio Services limits

The following table lists the recommended guidelines for instances of Visio Services in SharePoint Server 2013.
Limit Maximum value Limit type Notes
File size of Visio web drawings50 MBThresholdVisio Services has a configuration setting that enables the administrator to change the maximum size of web drawings that Visio processes.
Larger file sizes have the following side effects:
  • Increase in the memory footprint of Visio Services.
  • Increase in CPU usage.
  • Reduction in application server requests per second.
  • Increase overall latency.
  • Increase SharePoint farm network load
Visio web drawing recalculation time-out120 secondsThresholdVisio Services has a configuration setting that enables the administrator to change the maximum time that it can spend recalculating a drawing after a data refresh.
A larger recalculation time-out leads to:
  • Reduction in CPU and memory availability.
  • Reduction in application requests per second.
  • Increase in average latency across all documents.
A smaller recalculation time-out leads to:
  • Reduction of the complexity of diagrams that can be displayed.
  • Increase in requests per second.
  • Decrease in average latency across all documents.
Visio Services minimum cache age (data connected diagrams)Minimum cache age: 0 to 24hrsThresholdMinimum cache age applies to data connected diagrams. It determines the earliest point at which the current diagram can be removed from cache.
Setting Min Cache Age to a very low value will reduce throughput and increase latency, because invalidating the cache too often forces Visio to recalculate often and reduces CPU and memory availability.
Visio Services maximum cache age (non-data connected diagrams)Maximum cache age: 0 to 24hrsThresholdMaximum cache age applies to non-data connected diagrams. This value determines how long to keep the current diagram in memory.
Increasing Max Cache Age decreases latency for commonly requested drawings.
However, setting Max Cache Age to a very high value increases latency and slows throughput for items that are not cached, because the items already in cache consume and reduce available memory.

SharePoint Web Analytics service limits

The SharePoint Web Analytics service has been deprecated in SharePoint Server 2013.

PerformancePoint Services limits

The following table lists the recommended guidelines for PerformancePoint Services in SharePoint Server 2013.
Limit Maximum value Limit type Notes
Cells1,000,000 per query on Excel Services data sourceBoundaryA PerformancePoint scorecard that calls an Excel Services data source is subject to a limit of no more than 1,000,000 cells per query.
Columns and rows15 columns by 60,000 rowsThresholdThe maximum number of columns and rows when rendering any PerformancePoint dashboard object that uses a Excel workbook as a data source. The number of rows could change based on the number of columns.
Query on a SharePoint list15 columns by 5,000 rowsSupportedThe maximum number of columns and row when rendering any PerformancePoint dashboard object that uses a SharePoint list as a data source. The number of rows could change based on the number of columns.
Query on a SQL Server data source15 columns by 20,000 rowsSupportedThe maximum number of columns and row when rendering any PerformancePoint dashboard object that uses a SQL Server table data source. The number of rows could change based on the number of columns.

Word Automation Services limits

The following table lists the recommended guidelines for Word Automation Services.
Limit Maximum value Limit type Notes
Input file Size512 MBBoundaryMaximum file size that can be processed by Word Automation Services.
Frequency with which to start conversions (minutes)1 minute (recommended)
15 minutes (default)
59 minutes (boundary)
ThresholdThis setting determines how often the Word Automation Services timer job executes. A lower number leads to the timer job running faster. Our testing shows that it is most useful to run this timer job once per minute.
Number of conversions to start per conversion processFor PDF/XPS output formats: 30 x MFor all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)ThresholdThe number of conversions to start affects the throughput of Word Automation Services.
If these values are set higher than the recommended levels then some conversion items may start to fail intermittently and user permissions may expire. User permissions expire 24 hours from the time that a conversion job is started.
Conversion job size100,000 conversion itemsSupportedA conversion job includes one or more conversion items, each of which represents a single conversion to be performed on a single input file in SharePoint. When a conversion job is started (using the ConversionJob.Start method), the conversion job and all conversion items are transmitted over to an application server which then stores the job in the Word Automation Services database. A large number of conversion items will increase both the execution time of the Start method and the number of bytes transmitted to the application server.
Total active conversion processesN-1, where N is the number of cores on each application serverThresholdAn active conversion process can consume a single processing core. Therefore, customers should not run more conversion processes than they have processing cores in their application servers.  The conversion timer job and other SharePoint activities also require occasional use of a processing core.
We recommend that you always leave 1 core free for use by the conversion timer job and SharePoint.
Word Automation Services database size2 million conversion itemsSupportedWord Automation Services maintains a persistent queue of conversion items in its database. Each conversion request generates one or more records.
Word Automation Services does not delete records from the database automatically, so the database can grow indefinitely without maintenance. Administrators can manually remove conversion job history by using the Windows PowerShell cmdlet Remove-SPWordConversionServiceJobHistory. For more information, see Remove-SPWordConversionServiceJobHistory.

Excel Services limits

The following table lists the recommended guidelines for Excel Services in SharePoint Server 2013.
Limit Maximum value Limit type Notes
Maximum workbook size10 MBSupportedThe maximum size of a workbook that can be opened in Excel Services is 10 megabytes.

Machine Translation Service limits

The following table lists the recommended guidelines for the Machine Translation Service.
Limit Maximum value Limit type Notes
Input file size for binary files524,288 KB per fileThresholdFiles larger than the limit take too long to transfer and process, decreasing the throughput of the service.
Input file size for text files15,360 KB per fileThresholdFiles larger than the limit have too much text to translate, decreasing the throughput of the service.
Maximum character count for Microsoft Word Documents10,000,000 per documentThresholdDocuments with more characters than the limit have too much text to translate, decreasing the throughput of the service.
Total concurrent translation processes5ThresholdUsing more processes than the limit does not increase throughput because there is a limit to how much text can be translated at a time.  Using more processes increases the demands on the server resources.
Delay between translations59 minutesThresholdStarting translations at a larger interval than the limit causes the time taken to translate documents to grow too large and can cause the number of queued translations to grow too large.
Number of translations per translation process1,000 per processThresholdStarting more translations than the limit causes translations to fail due to timing out because they cannot be processed before the timeout period.
Maximum concurrent translation requests300ThresholdMore than 300 concurrent translation requests could cause translations to time out because requests are queued for longer than the timeout period.
Files per translation job100,000 filesSupportedSubmitting jobs with a number of files that exceeds the limit causes job submittal time and processing time to be too long.
Machine Translation Service database size1,000,000 filesSupportedOperations to maintain the queue of jobs become slow if the database grows beyond the maximum number of files in the database.

Office Web Application Service limits

The following table lists the recommended guidelines for Office Web Apps. Office client application limits also apply when an application is running as a web app.
Limit Maximum value Limit type Notes
Cache size100 GBThresholdSpace available to render documents, created as part of a content database. By default, the cache available to render documents is 100 GB. We do not recommend that you increase the available cache.
RendersOne per document per second per CPU core per application server (maximum eight cores)BoundaryThis is the measured average number of renders that can be performed of "typical" documents on the application server over a period of time.
OneNote concurrent merge operations8 per documentThresholdOneNote merges combine changes from multiple users who are co-authoring a notebook. If too many concurrent merges are already in progress, a conflict page is generated instead, which forces the user to perform the merge manually.

Project Server limits

The following table lists the recommended guidelines for Project Server. For more information about how to plan for Project Server, see Plan for Project Server 2013.
Limit Maximum value Limit type Notes
End of project timeDate: 12/31/2149BoundaryProject plans cannot extend past the date 12/31/2149.
Deliverables per project plan1,500 deliverablesBoundaryProject plans cannot contain more than 1,500 deliverables.
Number of fields in a view256BoundaryA user cannot have more than 256 fields added to a view that they have defined in Project Web App.
Number of clauses in a filter for a view50BoundaryA user cannot add a filter to a view that has more than 50 clauses in it.

SharePoint Apps limits

The following table lists the recommended guidelines for apps for SharePoint.
Limit Maximum value Limit type Notes
Maximum Access app size on Office 365/SQL Azure100 MbBoundary100 MB is the limit for Access apps created on Office 365 and for packages that can be created from these apps.
Apps displayed in Manage Licenses page2,000BoundaryUp to 2,000 apps (purchased from the store) can be displayed on the Manage Licenses page. You can still manage the license of any app by going to the All Site Contents page of the site where the app is installed and clicking on Licenses, or by searching for the app using Marketplace Search.
Number of app licenses per tenant1,000,000SupportedThe maximum supported number of licenses (purchase of apps from the store) for a single SharePoint deployment, either on-premises or SharePoint Online. Exceeding this limit might cause severe performance degradation.
Number of apps displayed in the Add an App page240BoundaryAfter this limit is reached, only the first 240 apps are displayed, and a message guiding you to search to find your app is displayed.
Number of managers per app license30BoundaryOnly 30 people can manage a license. License managers can add or remove users or delete a license.
Number of app licenses assigned to a user viewable by that user2,000BoundaryWhen more than 2,000 licenses are assigned to a user, that user will no longer see any apps in the default Add an App view. Instead, a message guiding you to search the app catalog or the SharePoint Store will appear.
Number of apps in the corporate catalog viewable by a single user500BoundaryWhen more than 500 apps from the corporate catalog are available to a single user, that user will no longer see any apps in the default Add an App view. Instead, a message guiding you to search the app catalog or the SharePoint Store will appear.

Distributed cache service limits

The following table lists the recommended guidelines for the distributed cache service.
Limit Maximum value Limit type Notes
Number of followable entities (users, documents, sites and hashtags) per cache host400,000SupportedThe total number of entities that can be followed by a single user on a distributed cache host with 16GB RAM assigned to the distributed cache service is 400,000.
Number of cache hosts in a cluster16BoundaryThe total number of cache hosts a single distributed cache cluster can support is 16.
Maximum amount of memory dedicated to a cache host16GBBoundaryThe total amount of memory that can be dedicated to the distributed cache service on any one cache host in a cluster is 16GB.

Miscellaneous limits

The following table lists limits and recommended guidelines for services and features not covered in other sections.
Limit Maximum value Limit type Notes
Number of User agent substrings per device channel150BoundaryThe maximum number of user agent substrings per mobile device channel is 150.
Number of SharePoint sources per EDiscovery case100BoundaryThe maximum number of SharePoint sources that can be added to an EDiscovery case is 100.
Number of Exchange sources (mailboxes) per EDiscovery case1,500BoundaryThe maximum number of Exchange sources (mailboxes) per EDiscovery case is 1,500.
Maximum size of EDiscovery Query16K characters or 500 keywordsBoundaryThe size of an EDiscovery query is limited to 500 keywords or 16,000 characters, whichever is reached first.
Number of nodes in managed navigation term set2,000SupportedThe maximum supported number of terms in a managed navigation term set is 2,000.

No comments: