Thread pool configurations are applicable to java processes that run-in diameter-endpoint-s1xx on Director VM and binding-s1xx container on Worker VMs in DRA.

For more information on Threading Configuration, refer to the CPS vDRA Configuration Guide.

The following tables lists recommended values when single DRA installation TPS is above 200 K.

Important

The highlighted values must be explicitly configured.

Note	Rated database capacity has been arrived at after performing capacity tests.

The following table lists the database capacity for small and large deployments.

The following is the test call model used to determine the capacity for each cluster:

1. CCR_I, CCR_T and AAR call model for Session-IPv6 database cluster capacity.

2. CCR-I and CCR_T call model for IMSI-APN/MSISDN-APN database cluster capacity.

3. Database capacity is based on network latency mentioned in the Table 1. If network latency is changed to higher value, then database capacity needs to be re-characterized.

Database alerts refer to alerts that can be configured to be triggered if the capacity of the database exceeds beyond a certain threshold.

The following configurations vary based on deployment size (Small or Large) and should be configured accordingly. The worker VM java processes connect to the databases and create two database connection pools based on the database operation:

• Create/Update, and Delete

• Read

For more information on configuration syntax and examples, refer to the CPS vDRA Operations Guide.

binding db-connection-settings

The recommended values listed in the table are for write operations (Create/Update, Delete):

Important

The highlighted values must be explicitly configured.

Table 4. Recommended Value for Write Operations

Deployment	Bindings	connection-per-host
		Default Values	Recommended Values
Small Deployment	drasession	10	14
	ipv6	10	10
	imsiapn	10	35
	msisdnapn	10	10
	ipv4	10	10
Large Deployment	drasession	10	10
	ipv6	10	10
	imsiapn	10	20
	msisdnapn	10	20
	ipv4	10	2

binding db-read-connection-settings

The recommended values listed in the table are for read operations:

Important

The highlighted values must be explicitly configured.

Table 5. Recommended Value for Read Operations

Deployment	Bindings	connections-per-host-for-read
		Default Values	Recommended Values
Small Deployment	drasession	5	5
	ipv6	5	5
	imsiapn	5	3
	msisdnapn	5	5
	ipv4	5	5
Large Deployment	drasession	5	20
	ipv6	5	20
	imsiapn	5	10
	msisdnapn	5	10
	ipv4	5	1

Database Audit is an important functionality in DRA. To ensure that the database does not fill up with unnecessary entries or expired entries are cleared, a house keeping process is always functional. The following parameters should be used based on the deployment size and rated capacity of the system.

Director nodes periodically advertise the status of all its peer connections over local and global control plane. All DRA nodes in the network use these peer status messages to keep their peer topology view updated. Peer topology is used to route the messages to appropriate director across different sites. When there are large number of peers connected across different sites, the load on control plane increases. This load increase can cause delay in processing peer status updates.

The following configurations are recommended to handle the increase in the control plane traffic process.

DRA maintains an IPC message queue where all the internal messages exchanged between Directors or Workers are stored. There are a set of IPC Queue processor threads that process these messages. During slow network conditions, when messages get delivered to one or a subset of peers, an IPC Queue processor thread that sends the message to these peers can eventually degrade the rate at which the IPC messages drop. These slow down conditions can cause message drops and 3002 errors not only to peers having degraded network but also to other peers.

The following configurations are recommended to handle the slow network peers.

Note

To disable the SLA timeout, configure lock-sla-timeout to 2000 ms. Disabling SLA timeout leads to ipc message drop in slow network. To disable throttling, configure message-throttle-duration to 0. To disable thread throttling(limit), configure it to the value same as IPC Processor threads. Increasing timeout-sample-to-throttle reduces the chance of throttling the peer.

The enhancement of the slow peer handling logic is applicable for priority and nonpriority messages. Once a slow peer is identified, the application must be notified. The further messages towards that peer will be throttled for the configured duration (message-throttle-duration). Once the configured time elapsed, the peer will be marked as normal peer and all the messages towards that peer will be processed.

The following configurations are recommended to handle the slow network peers with extra optional parameters.