Replication latency is the amount of time it takes for a transaction to be applied to the replicate database from the primary database. The latency threads table describes the threads that represent the latency chart in the path dashboard.
| Latency Thread | Description |
|---|---|
| Replication Executor Thread (EXEC) | The number of seconds from the start, to time the ticket passes through the EXEC thread. |
| Distribution (DIST) Thread | The number of seconds from the primary Replication Server time to the time the ticket passes through the DIST thread. For each primary database managed by a Replication Server, there is a DIST, which in turn uses Stable Queue Transaction (SQT) to read from the inbound queue, and Stable Queue Manager (SQM) threads to write transactions to the outbound queue. |
| Replication Server Interface (RSI) Thread | The number of seconds from the DIST thread time to the time the ticket passes through the RSI thread. RSI threads send messages from one Replication Server to another. There is one RSI thread for each destination Replication Server. |
| Data Server Interface (DSI) Thread | The number of seconds from the RSI thread time to the time the ticket passes through the DSI thread. The DSI thread translates the transaction modifications into remote procedure calls (RPC) or the language as specified by the function strings in the function-string class assigned to the destination database. Replication Server starts the DSI threads to submit transactions to a replicate database to which it has a connection. |
| Replicate Database | The number of seconds from the DSI thread time to the time the ticket arrived at the replicate database. |
| Total Latency | The number of seconds between the time at origin and destination for the transaction committed. |