ControlPoint Discovery is task that collects cached information for data analysis and reporting.
Because Discovery is a resource-intensive process, it is configured to pause at regular intervals to allow other processes to access a greater share of the machine's CPU and disk resources.
ControlPoint Application Administrators can change this pause time by modifying the Value of the ControlPoint Settings Discovery Pause Time to Allow Other Operations. This value represents the number of milliseconds that Discovery pauses to let other processes proceed.
If the Discovery Pause Time to Allow Other Operations value is decreased, the Discovery process will take less time to complete, but users will experience slower response times while it runs. Conversely, if this value is increased, the Discovery process will take longer to complete, but users will experience faster response times.
TIP: If Discovery is run only as a nightly process and system usage is low at that time, the default value is usually sufficient. If Discovery is run manually while users are active, and/or usage is high when nightly Discovery is run, it may be advantageous to increase the Discovery Pause Time to Allow Other Operations time.
As of version 5.2.345.0, Full Discovery can run a maximum of 1260 minutes (21 hours) at one time. If ControlPoint has a particularly large farm to discover and Discovery has not completed within that timeframe, it will continue where it left off the next time it is run, either manually or on schedule. ControlPoint Application Administrators may want to decrease the time restrictionto ensure that Discovery is not consuming system resources during peak usage timesby updating the Value of the ControlPoint Configuration Setting Maximum Discovery Run Time.
NOTE: If the Value is blank, Full Discovery will be processed in a single run.
The location within a site collection where Discovery will stop when the time restriction is reached is determined by the Configuration Setting Depth at Which to Stop Discovery When Time Restriction is Reached.
As of version 6.0. the default value of the ControlPoint Setting Tuning Options to Improve Discovery Performance is PDA:. Each component of this value is described in the following table.
Value Component |
Description |
---|---|
P |
Partial Discovery does not discover the following elements within a site collection if they have not changed: ·activity ·permissions of all SharePoint users ·Web parts, and ·SharePoint permissions for members of the Business Administrators group |
D |
Full Discovery does not discover the following elements within a site collection if they have not changed: ·activity ·permissions of all SharePoint users ·Web parts, and ·SharePoint permissions for members of the Business Administrators group |
A |
All activity is calculated at the end of Discovery (which requires fewer queries for better performance) |
If ControlPoint was initially installed prior to version 6.0, it is recommended that the Value be set to PDA to optimize Discovery performance.
By default, the ControlPoint Full Discovery process runs on all site collections within your SharePoint farm. ControlPoint Application Administrations can, however, exclude site collections whose url contains a specified text string from both the nightly Full Discovery process and any manual Discovery that is run on the entire farm. (Administrators still have the option of running a Partial Discovery on these site collections, either as-needed or on a one-time or recurring schedule).
Remember that data in analyses run from cache can only be reported up to the date of the last Discovery
To exclude site collections that contain a particular text string from the Full Discovery process, enter the string as the Value for the ControlPoint Setting Site Collections to Exclude from Full Discovery. Enter multiple text strings as a comma-separated list.
CAUTION: If any part of a site collection's url contains the text string you specified, it will be excluded from Full Discovery. Use caution in selecting strings to be sure you do not exclude more than you intend. For example, the excluded string of "Test" would exclude "My Test Site Collection" but would also exclude "Product Testing."
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center