Sizing and performance guidelines

Adaptive Authentication provides customers access to their on-premises authentication servers using either Cloud Connectors deployed in their data centers or Azure VNet Peering in case data center reachability is already established from the customer managed VNet. This topic contains information on the performance numbers for both Citrix Cloud Connector and Azure VNet Peering deployments and also the recommended scale and size configurations for Citrix Cloud Connector machines.

User authentication rate

A connector virtual machine of size 2 vCPUs and 7 GB RAM can authenticate 14 users/sec.

By default, the connector service is configured to auto-restart twice if there’s a failure or a crash. In the subsequent failure or a crash, the service stops. Also currently, the connector service fails if the authentication rate is increased beyond 4 authentications/sec. This rate can be achieved by configuring the connector service to restart after any number of failures (Citrix Netscaler Cloud Gateway > Recovery > Restart the service). If this setting isn’t configured, the rate drops to 4 authentications/sec.

Traffic latency and user authentication rate when using Citrix Cloud Connectors

The following table displays the traffic latency and the user authentication rate when using Citrix Cloud Connectors:

Authentication type Authentication latency (p95) in ms Authentication or user login rate per second
LDAP 5.99 14
RADIUS 3.17 14
LDAP+RADIUS 4.59 14
LDAPS 26.75 14
LDAPS+RADIUS 15.61 14

Traffic latency and user authentication rate when using Azure VNet Peering

The following table displays the traffic latency and the user authentication rate when using Azure VNet peering:

Authentication type Request latency(p95) in ms Authentication or user login rate per second
LDAP 6.95 17.54
LDAPS 7.19 16.98
Sizing and performance guidelines