Active Roles 8.2 - Best Practices Guide

Performance bottlenecks > Common SQL bottlenecks

When using Active Roles, consider the following possible SQL bottlenecks:

Database locks. Too many Active Roles services using the same shared database might cause deadlocks on tables, which will impact performance. In such cases, users could see delays in the Active Roles clients.
Geographic latency.
Insufficient resources, such as memory or hard disk.
Replication. Use SQL Replication Monitor to view and resolve any errors with SQL replication. For assistance with SQL replication, contact Microsoft.

Performance bottlenecks > Common memory bottlenecks

When using Active Roles, consider that the following features and components might cause increased memory usage:

Performance bottlenecks > Hard drive space bottlenecks

Consider the following settings, because they can occupy a large amount of hard drive space on the Active Roles hosts:

Limited page file size

One Identity recommends using the System managed size setting regardless of the amount of memory installed on the host.
To change the settings of the page file size
1. To open the Run command window, press Windows+R.
2. In the text box, type SystemPropertiesAdvanced.exe and press Enter.
3. Under Performance, click Settings.
4. In the Performance Options window, select the Advanced tab.
5. Under Virtual Memory, click Change.
Logging

Enabling Active Roles Verbose logging might result in a very large log file. One Identity recommends enabling Verbose logging only for troubleshooting purposes. For more information on logging, see Enabling or disabling diagnostic logs in the Active Roles Administration Guide.

Performance bottlenecks > CPU, network, third-party integration and Azure integration bottlenecks

When using Active Roles, consider the following processor, network, and integration-related bottlenecks.

CPU-intensive tasks, load balancers, proxies and network connections can cause performance bottlenecks across all Active Roles clients.
For third-party add-ons and integrations, ensure that the installed version is valid for the Active Roles version that you use, especially after upgrading Active Roles.
The number of Azure objects that you manage can impact overall performance in the Web Interface. Connectivity to Azure might be negatively impacted by load balancers, proxies and the general quality of the network connection.