SharePoint 2010 Limitations – Word Automation Services Limit

Word Automation Services Limit

Limit Maximum value Limit type Notes
Input file Size 512 MB Boundary Maximum 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)

Threshold 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.
Number of conversions to start per conversion process For 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) Threshold The 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 size 100,000 conversion items Supported 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 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 processes N-1, where N is the number of cores on each application server

 

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

We recommend that you always leave 1 core free for use by the conversion timer job and SharePoint.

Word Automation Services database size 2 million conversion items Supported Word 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.

Advertisements

SharePoint 2010 Limitations – Performance Point Services Limit Maximum value

Performance Point Services Limit Maximum value

Limit Maximum value Limit type Notes
Cells 1,000,000 per query on Excel Services data source Boundary A 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 rows 15 columns by 60,000 rows Threshold The maximum number of columns and rows when rendering any PerformancePoint dashboard object that uses a Microsoft Excel workbook as a data source. The number of rows could change based on the number of columns.
Query on a SharePoint list 15 columns by 5,000 rows Supported The 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 source 15 columns by 20,000 rows Supported The 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.

SharePoint 2010 Limitations – Visio Services Limit Maximum value

Visio Services Limit Maximum value

Limit Maximum value Limit type Notes
File size of Visio Web drawings 50 MB Threshold Visio 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-out 120 seconds Threshold Visio 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 24hrs Threshold Minimum 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 24hrs Threshold Maximum 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.