-This article describes software boundaries and limits of SharePoint Servers 2016 and 2019 which include:

-The test results and guidelines provided in this article apply to a single SharePoint Server 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](#Limits) 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.

-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.

-In SharePoint Server, 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.

- An example of a boundary is the 10-gigabyte (GB) document size limit; you cannot configure SharePoint Server 2016 to store documents that are larger than 10 GB. This boundary is a built-in absolute value, and cannot be exceeded by design.

- 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.

-It is important to know 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 2016 can be changed, but it is important to understand how changing a given limit affects other parts of the farm.

-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.

-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.

-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.

-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.

-|Number of content databases <br/> |500 per farm <br/> |Supported <br/> |The 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 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. <br/> With 200GB per content database, and 500 content databases per farm, SharePoint Server 2016 supports 100TB of data per farm. <br/> |

-|Content database size (general usage scenarios) <br/> |200 GB per content database <br/> |Supported <br/> |We strongly recommended limiting the size of content databases to 200 GB, except when the circumstances in the following rows in this table apply. <br/> If you are using Remote BLOB Storage (RBS), the total volume of remote BLOB storage and metadata in the content database must not exceed the 200GB limit. <br/> |

-|Content database size (all usage scenarios) <br/> |4 TB per content database <br/> |Supported <br/> | Content databases of up to 4 TB are supported when the following requirements are met: <br/> Disk sub-system performance of 0.25 IOPS per GB. 2 IOPs per GB are recommended for optimal performance. <br/> You must have developed plans for high availability, disaster recovery, future capacity, and performance testing. <br/> You should also carefully consider the following factors: <br/> Requirements for backup and restore may not be met by the native SharePoint Server 2016 backup for content databases larger than 200 GB. It is recommended to evaluate and test SharePoint Server 2016 backup and alternative backup solutions to determine the best solution for your specific environment. <br/> It is strongly recommended to have proactive skilled administrator management of the SharePoint Server 2016 and SQL Server installations. <br/> The complexity of customizations and configurations on SharePoint Server 2016 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. <br/> Refactoring of site collections allows for scale out of a SharePoint Server 2016 implementation across multiple content databases. This permits SharePoint Server 2016 implementations to scale indefinitely. This refactoring will be easier and faster when content databases are less than 200 GB. <br/> 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](software-boundaries-limits-2019.md#SiteCollection). <br/> **Important**: We do not recommend the use of content databases that exceed 4 Terabytes (TB), except in document archive scenarios (described in the next row in this table). If, in the future, you need to upgrade your SharePoint Server 2016 installation, upgrading the site collections within the content databases can 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) <br/> |No explicit content database limit <br/> |Supported <br/> | Content databases with no explicit size limit for use in document archive scenarios are supported when the following requirements are met: <br/> 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. <br/> SharePoint Server 2016 sites must be based on **Document Center** or **Records Center** site templates. <br/> 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. <br/> Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint Server 2016 objects in the content database. <br/> > [!NOTE]> Document archive content databases can be configured to accept documents from Content Routing workflows. |

-|Site collections per content database <br/> |10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone) <br/> |Supported <br/> |We 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. 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. <br/> 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. <br/> 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. <br/> 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. <br/> To set the warning and maximum levels for the number of sites in a content database, use the PowerShell cmdlet Set-SPContentDatabase with the **WarningSiteCount** parameter. For more information, see [Set-SPContentDatabase](/powershell/module/sharepoint-server/Set-SPContentDatabase?view=sharepoint-ps&preserve-view=true). <br/> |

-|Site collections per farm <br/> |250,000 per site collection / 500,000 Personal Sites/ 250,000 other sites per farm. <br/> |Supported <br/> |The 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. <br/> 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. <br/> 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. <br/> 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. <br/> |

-|Web site <br/> |250,000 per site collection / 250,000 per farm / 500,000 personal sites per farm. <br/> |Supported <br/> | Although the supported limit for the number of web sites in a site collection is 250,000 the recommended limit is 2,000. <br/> Performance can degrade as the number of web sites surpasses 2,000 in a site collection. <br/> **Important**: Staying below 2,000 web sites per site collection is strongly recommended. You can create a very large total number of web sites by creating multiple site collections with up to 2000 web sites per site collection. For example, 125 site collections that contain 2,000 web sites each will equate to 250,000 web sites in the farm. This would be considered the maximum recommended limit for non-personal sites. <br/> If you have 250,000 site collections, all containing a root web site that is not the Personal Site template, adding a sub-web site to any of those root web sites would exceed the 250,000 web site boundary. <br/> If the recommended limit of 2,000 web sites per site collection is exceeded, the following issues may occur: <br/> Deleting or creating a web site can affect the availability of other web sites in the same site collection. Access to the web sites in the site collection will be limited while the web site is being deleted. Attempting to create many web sites at the same time may also fail. <br/> When having more than 2,000 web sites, the performance of actions such as executing PSConfig when adding a new server to an existing farm or after installing SharePoint updates then drastically decrease. <br/> Executing the **stsadm -o checklocalupgradestatus** operation or the daily execution of the **Product Version Job** timer job may take many hours to complete. <br/> Browsing the **Review database status** page (<your_SharePoint_CentralAdmin_URL>/_admin/UpgradeStatus.aspx) on the Central Administration web site may result in a timeout. <br/> |

-|Minor versions <br/> |511 <br/> |Boundary <br/> |The maximum number of minor file versions is 511. This limit cannot be exceeded. <br/> |

-|List view lookup threshold <br/> |12 join operations per query <br/> |Threshold <br/> |Specifies 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 12 lookups. <br/> |

-|List view threshold for auditors and administrators <br/> |20,000 <br/> |Threshold <br/> |Specifies 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. <br/> |

-|Subsite <br/> |2,000 per site view <br/> |Threshold <br/> |The 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. <br/> |

-|Security scope <br/> |50,000 per list <br/> |Threshold <br/> |The maximum number of unique security scopes set for a list cannot exceed 50,000. <br/> For most farms, we recommend that you consider lowering this limit to 5,000 unique scopes. For large lists, consider using a design that uses as few unique permissions as possible. <br/> When the number of unique security scopes for a list exceeds the value of the list view threshold (set by default at 5,000 list items), additional SQL Server round trips take place when the list is viewed, which can adversely affect list view performance. <br/> 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 2016. 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. <br/> |

-|Security scope (ACL) propagation <br/> |500 child objects with unique scopes <br/> |Threshold <br/> |The maximum number of child objects with unique security scopes that can be updated during ACL propagation cannot exceed 500. <br/> Scope updates can be set to update child objects using ACL propagation, which will update uniquely scoped items and items that inherit permissions. During a parent scope update that includes ACL propagation to children, if the maximum number of child objects with unique scopes is greater than 500, propagation will fail with only some of the children with unique scopes potentially being updated. Whenever the maximum number of child objects with unique scopes is larger than 500 ACL propagation should not be used. <br/> |

-SharePoint Server 2016 data is stored in SQL Server tables. Each column type has a size value listed in bytes. The sum of all columns in a SharePoint list cannot exceed 8,000 bytes.

-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:

-|Number of SharePoint groups a user can belong to <br/> |5,000 <br/> |Supported <br/> | This is not a hard limit but it is consistent with Active Directory guidelines. There are several things that affect this number: <br/> The size of the user token <br/> The groups cache: SharePoint Server 2016 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). <br/> 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. <br/> |

-|Security principal: size of the Security Scope <br/> |5,000 per Access Control List (ACL) <br/> |Supported <br/> |The 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. <br/> |

-|Analytics reporting databases <br/> |4 per Search service application <br/> |Threshold <br/> |You can exceed this limit to accommodate specific requirements. When scaling, add an analytics reporting database when the size of any of the deployed analytics databases reaches 250 GB total size, or 20 M total rows. This way repartitioning is as balanced as possible. <br/> |

-|Content processing components <br/> |1 per server <br/> |Supported <br/> |The search 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 according to 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. <br/> 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 Server 2016 limits the value of N upward 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. <br/> In the case that there still is idle CPU time, consider increasing the K coefficient instead of adding an additional content processing component. If you increase the K coefficient, you must make sure that the host has sufficient available memory. <br/> |

-|Search components <br/> |64 per Search service application <br/> |Supported <br/> |This limit does not include crawl components. The sum of all the other search components must stay within this limit. <br/> |

-|Content sources <br/> |500 per Search service application <br/> |Boundary <br/> |There is overhead associated with each content source, so we recommend that you create the smallest number of content sources that satisfy your other operational requirements, for example differences in crawl priority and scheduling. <br/> |

-|Document size crawl component can download <br/> |64 MB (4 MB for Excel documents) <br/> |Threshold <br/> |Search downloads meta data and content from a document until it reaches the maximum document size. The rest of the content is not downloaded. Search always downloads a document's meta data. <br/> You can change the default limit for the maximum document size. Do this by using Microsoft PowerShell cmdlets to change the Search service application property **MaxDownLoadSize** or **MaxDownloadSizeExcel**. **MaxDownLoadSize** doesn't impact the maximum size for Excel documents. Enter the value in megabytes. The maximum value for the maximum document size is 1024 MB, also for Excel documents. <br/> If you increase the limit for the maximum document size, search indexes more content and needs more disk space. <br/> |

-|Unique indexed tokens per managed property <br/> |1,000,000 <br/> |Threshold <br/> |This limit type is the maximum number of unique tokens that can be added to the search index per managed property. This limit can't be changed. If the limit is exceeded, the index will contain the first 1,000,000 tokens from the managed property and the file will be marked as partially processed by setting the IsPartiallyProcessed property to true. Exception: If the limit is reached for an ACL related managed property, no tokens from that managed property are added to the index. <br/> |

-|Content deployment jobs running on different paths <br/> |20 <br/> |Supported <br/> |For 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. <br/> **Note**: 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 snapshot-path correlation increases the I/O requirements for the source database. <br/> For more information, see [About deployment paths and jobs](/previous-versions/office/sharepoint-server-2010/ee721058(v=office.14)#section2a). <br/> |

-|External system connections <br/> |500 per web server <br/> |Boundary <br/> |Number 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. <br/> |

-|Database items returned per request <br/> |2,000 per database connector <br/> |Threshold <br/> |Number of items per request the database connector can return. <br/> The default maximum of 2,000 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 maximum even for applications that do not respect the default. The boundary for this limit is 1,000,000. <br/> |

-|Database Item <br/> |1,000,000 per request <br/> |Threshold <br/> |The default maximum number of items per request the database connector can return is 2,000, and the absolute maximum is 1,000,000. <br/> 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. <br/> |

-|Workflow postpone threshold <br/> |15 <br/> |Threshold <br/> |15 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 limit can be configured by using the Set-SPFarmConfig PowerShell cmdlet. For more information, see [Set-SPFarmConfig](/powershell/module/sharepoint-server/Set-SPFarmConfig). <br/> 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. <br/> |

-|Workflow timer batch size <br/> |100 <br/> |Threshold <br/> |The number of events that each run of the workflow timer job will collect and deliver to workflows. It is configurable by using PowerShell. To allow for more events, you can run more instances of the SharePoint Foundation Workflow Timer Service. <br/> |

-|Workflow associations <br/> |100 per list <br/> |Supported <br/> |Exceeding 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. <br/> |

-|Maximum workflow definition (xaml) size <br/> |5,120 KB <br/> |Boundary <br/> |Attempts to publish xaml files that exceed the size limit will fail. <br/> |

-|Maximum depth of a workflow substep in xaml (workflow complexity) <br/> |121 levels <br/> |Boundary <br/> |There 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. <br/> |

-|Workflow instance activations per second per web server <br/> |6 per second <br/> |Threshold <br/> |Testing has confirmed that a SharePoint web server can activate a maximum of six workflow instances per second. This number is cumulative, and therefore scales with the number of web servers in the farm. For example, two web servers can activate 12 workflow instances per second, and three web servers can activate 18. <br/> |

-|Workflow variable value size <br/> |256 KB <br/> |Boundary <br/> |The 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. <br/> |

-|Maximum list size for workflow lookups to non-indexed fields <br/> |5,000 items per list view <br/> |Threshold <br/> |This 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. <br/> |

-|Maximum list size for autostart workflow associations <br/> |10 million items per list <br/> |Supported <br/> |Testing has confirmed that the performance of autostart 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. <br/> |

-|Maximum number of terms in a term set <br/> |30,000 <br/> |Supported <br/> |30,000 is the maximum number of terms in a term set. <br/> **Note**: Extra labels for the same term, such as synonyms and translations, do not count as separate terms. |

-|Total number of items in a term store <br/> |1,000,000 <br/> |Supported <br/> |An 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. <br/> **Note**: You cannot have both the maximum number of term sets and the maximum number of terms simultaneously in a term store. |

-|Visio Services minimum cache age (data connected diagrams) <br/> |Minimum cache age: 0 to 24 hrs <br/> |Threshold <br/> |Minimum cache age applies to data connected diagrams. It determines the earliest point at which the current diagram can be removed from cache. <br/> Setting Min Cache Age to a 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. <br/> |

-|Visio Services maximum cache age (non-data connected diagrams) <br/> |Maximum cache age: 0 to 24 hrs <br/> |Threshold <br/> |Maximum cache age applies to non-data connected diagrams. This value determines how long to keep the current diagram in memory. <br/> Increasing Max Cache Age decreases latency for commonly requested drawings. <br/> However, setting Max Cache Age to a high value increases latency and slows throughput for items that are not cached, because the items already in cache consume and reduce available memory. <br/> |

-|Frequency with which to start conversions (minutes) <br/> |1 minute (recommended) <br/> 15 minutes (default) <br/> 59 minutes (boundary) <br/> |Threshold <br/> |This 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. <br/> |

-|Conversion job size <br/> |100,000 conversion items <br/> |Supported <br/> |A 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 that 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. <br/> |

-|Total active conversion processes <br/> |N-1, where N is the number of cores on each application server <br/> |Threshold <br/> |An 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. <br/> We recommend that you always leave one core free for use by the conversion timer job and SharePoint. <br/> |

-|Word Automation Services database size <br/> |2 million conversion items <br/> |Supported <br/> |Word Automation Services maintains a persistent queue of conversion items in its database. Each conversion request generates one or more records. <br/> 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 PowerShell cmdlet Remove-SPWordConversionServiceJobHistory. For more information, see [Remove-SPWordConversionServiceJobHistory](/powershell/module/sharepoint-server/Remove-SPWordConversionServiceJobHistory). <br/> |

-|Total concurrent translation processes <br/> |5 <br/> |Threshold <br/> |Using 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. <br/> |

-|Number of translations per translation process <br/> |1,000 per process <br/> |Threshold <br/> |Starting more translations than the limit causes translations to fail due to timing out because they cannot be processed before the timeout period. <br/> |

-|Cache size <br/> |100 GB <br/> |Threshold <br/> |Space 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. <br/> |

-|End of project time <br/> |Date: 12/31/2149 <br/> |Boundary <br/> |Project plans cannot extend past the date 12/31/2149. <br/> |

-|Deliverables per project plan <br/> |1,500 deliverables <br/> |Boundary <br/> |Project plans cannot contain more than 1,500 deliverables. <br/> |

-|Number of fields in a view <br/> |256 <br/> |Boundary <br/> |A user cannot have more than 256 fields added to a view that they have defined in Project Web App. <br/> |

-|Number of clauses in a filter for a view <br/> |50 <br/> |Boundary <br/> |A user cannot add a filter to a view that has more than 50 clauses in it. <br/> |

-|Number of followable entities (users, documents, sites and hashtags) per cache host <br/> |400,000 <br/> |Supported <br/> |The total number of entities that can be followed by a single user on a distributed cache host with 16 GB RAM assigned to the distributed cache service is 400,000. <br/> |

-## Related Topics