If sqm_cache_enable and dist_cmd_direct_replicate are on, and sqm_cmd_cache_size and sqm_max_cmd_in_block are set to nonzero values, you can use several counters to monitor replication performance, as the EXEC, DIST, and DSI threads and modules interact with the parsed data.
| Counter | Description |
|---|---|
| DISTCmdsDirectRepSend | Number of commands that are in parsed data format that are directly sent from the DIST module. |
| DSIECmdsDirectRepRecv | Number of commands received by the DSI-E thread directly from either the DIST module conveying outbound commands or the EXEC module conveying standby inbound commands. If the DSI module is for a warm standby connection, DSIECmdsDirectRepRecv counts inbound commands, otherwise DSIECmdsDirectRepRecv counts outbound commands. |
| SQMNoDirectReplicateInCache | The number of commands that have parsed data sent from the Distributor thread, but the parsed data cannot be sent further along the replication pathway towards the DSI thread because the command cache exceeds sqm_cmd_cache_size |
| SQMNoDirectReplicateInSQMCache | The number of commands that have parsed data sent from the Distributor thread, but the parsed data cannot be sent further along the replication pathway towards the DSI thread because these commands were overwritten in SQM cache before being read |
| SQMNoDirectReplicateInBlock | The number of commands that have parsed data sent from the Distributor thread, but the parsed data cannot be sent further along the replication pathway towards the DSI thread because the number of parsed data entries for the current SQM block exceeds sqm_max_cmd_in_block |