Number of replication threads

Edit online

You can tune the number of replication threads by setting the ibm-replicaconsumerconnections attribute with an appropriate value. The attribute value specifies the number of connections to use for each replication agreement.

If you increase the number of threads on both the supplier and consumer servers, the transaction rate also increases. In the following graph, a transaction is defined as a queued replication record that is sent to the supplier. In this example, the ldap_modify operation is used. The queued replication records (ldap_modify) are run with replication in the pending state. The replication state is then changed to resume, which starts the replication process.

Note: As the number of threads increases, the processor usage on both supplier and consumer systems increases. Tune the attribute as required based on an acceptable processor usage value and the required throughput.
Figure 1. The relationship between the number of replication threads and transactions per second

As the number of threads on both the supplier and consumer are increased, the number of transactions also increased.

If the throughput increases, the processor usage on both the supplier and consumer server increases. The processor cost per transaction on the consumer increases slightly when you add threads because there are more threads to manage now.