ControlPoint 8.6.1 - for Office 365 Administration Guide

Maximum Number of Objects to Processed in Parallel (MaxParallelProcs)

By default, ControlPoint Discovery processes up to two site collections/sites simultaneously, for improved performance over sequential processing.  For Actions and reports, sequential processing is used by default (that is, the objects involved (site collection, site, subsite, lists, and so on) are processed one at a time, in hierarchical order).  ControlPoint Application Administrators may, however, choose to

·increase or decrease the maximum number of objects that should be processed simultaneously (i.e., in parallel), and/or

·specify the operation(s) (Discovery, Actions, and/or Reports) for which parallel processing should/should not be used.

It is recommended the Maximum Number of Objects to Process in Parallel Value be set to the number of cores on the server machine where the processing occurs.

If you are encountering errors during the processing of operations for which parallel processing is used, it is recommended that you gradually decrease the Maximum Number of Objects to Process in Parallel Value.  

If the Maximum Number of Objects to Process in Parallel Value is set to 0 or 1, no parallel processing will occur (that is, objects for all operations will be processed sequentially).

NOTE:  If the value is greater than 1 and the value of Operations Using Parallel Processing (ParallelProcs) is blank, parallel processing will apply to Discovery.  Otherwise,it will apply to operations specified for

Operations Using Parallel Processing (ParallelProcs)

By default, ControlPoint Discovery processes up to two site collections/sites simultaneously, for improved performance over sequential processing.  For actions and reports, sequential processing is used by default (that is, the objects involved (site collection, site, subsite, lists, and so on) are processed one at a time, in hierarchical order).  ControlPoint Application Administrators may, however, choose to

·increase or decrease the maximum number of objects that should be processed simultaneously (i.e., in parallel), and/or

·specify the operation(s) (Discovery, Actions, and/or Reports) for which parallel processing should/should not be used.

Specify the operations for which parallel processing should be used by completing the Value of the ControlPoint Setting ParallelProcs with one or more of the following values:

·D (Discovery)

·A (Actions)

·R (Reports)

Enter multiple values as a comma-separated list.  

NOTE:  If the Operations Using Parallel Processing Value is blank, parallel processing will apply to Discovery only.

For this setting to be operational, the Value of the setting Maximum Number of Objects to Processed in Parallel.

Objects Subject to Parallel Processing (ParallelProcSites)

By default, when Maximum Number of Objects to Process in Parallel is set to a value greater than 1, ControlPoint processes operations in parallel at the site collection level.  ControlPoint Application Administrators can, however, have parallel operations processed at the site level by changing the Value of the ControlPoint Setting Objects Subject to Parallel Processing from false to true.

NOTE:  This is an Advanced Setting.

SQL Command Timeout Value (COMMANDTIMEOUT)

By default, the ControlPoint SQL Command timeout value is set to 300 seconds. This value represents the amount of time that ControlPoint will wait for a SQL command to run before issuing the following message:  

[Method Name]Timeout Exception:  The server has timed out.

The default value should be sufficient in most cases.  However, for an exceptionally large or busy farm, the ControlPoint Application Administrator may need to increase the Value of the ControlPoint Setting SQL Command Timeout Value.

NOTE:  This is an Advanced Setting.

NOTE:  Remember, this value is specified in seconds.