Reports the current throughput in terms of transactions, commands, or bytes per second.
admin stats, cps
Report Time: 10/31/05 02:58:54 PM Instance Observer Obs Rate x/sec ---------------------------------- ----- ---------- REP AGENT, pds01.tpcc *CmdsRecv 69876 0 (1 row affected) ================================================================= Report Time: 10/31/05 02:58:54 PM Instance Observer Obs Rate x/sec ------------------------------------------ ----- ----------- SQM, 101:0 edsprs01.edbprs01 *CmdsWritten 0 0 SQM, 102:0 pds01.tpcc *CmdsWritten 0 0 SQM, 102:1 pds01.tpcc *CmdsWritten 69886 25 SQM, 103:0 rds01.tpcc *CmdsWritten 48174 17 (4 rows affected) ========================================================================== Report Time: 10/31/05 02:58:54 PM Instance Observer Obs Rate x/sec ------------------------------------------------ ----------- ---------- SQMR, 101:0 edsprs01.edbprs01, 0, DSI *CmdsRead 0 0 SQMR, 102:0 pds01.tpcc, 0, DSI *CmdsRead 0 0 SQMR, 102:1 pds01.tpcc, 0, SQT *CmdsRead 50499 18 SQMR, 103:0 rds01.tpcc, 0, DSI *CmdsRead 48144 17 (4 rows affected) ======================================================================== ...
When calculating throughput per second, Replication Server bases the calculation on the number of processed transactions and the number of elapsed seconds since the counters were last reset using admin stats, reset.
Different modules report throughput for each type of calculation:
Transactions per second – are reported by the SQT, DIST, DSI, and other modules.
Commands per second – are reported by the RepAgent, RSIUSER, SQM, DIST, DSI, and RSI modules.
Bytes per second – are reported by the RepAgent, RSIUSER, SQM, DSI, and RSI modules. The SQM reports transactions in both bytes and blocks per second.