Answer

Integrations, by their very nature, interact with and thus create performance loads on the external tools that they connect.

Planview Hub provides several methods to control precisely how Hub integrations impact those external tools:

• Users can set an event rate limit in order to limit the number of events processed per minute by Hub in a repository. This can mitigate scenarios where the API call limit of an external tool has been met due to Hub integration processing.

• Users can set integration-specific change detection intervals. By utilizing a High Performance Full Scan, rather than a High Fidelity Full Scan, users can drastically reduce the number of REST API calls per minute. We strongly recommend reviewing this FAQ to learn more about the different change detection/full scan types and their impacts.

• Users can also extend the change detection and full scan intervals either globally or on an individual integration basis, to decrease the frequency with which Hub interacts with the external repositories.

• If the source of the high server load is specifically due to having too many open connections on the external repository, a Repository Concurrency Limit can be set to limit how much work Hub can do in parallel on that repository. Please review our user docs (linked above) to learn more about how to set a concurrency limit.

• If you are experiencing performance issues across all integrations, an Integration Maximum Concurrency Limit can be set.