Display Transactions Per Second
Follow this procedure to set how many transactions per second (TPS) the MATRIXX Engine servers or pods process. A TPS measure is useful to get a general idea of the health of the engine. Some print_engine_stats.py script TPS statistics are calculated for all engine servers or pods twice, the results are averaged, and the total for all servers or pods is returned. Other statistics only apply to the processing servers or pods, and those result tables are marked with an appropriate footnote.
About this task
Note: It is a good practice to
run the print_engine_stats.py script with the -e
engine parameter to ensure that the data returned is for the correct
engine.
Procedure
Run the following command to display the TPS for each server in an engine:
kubectl exec -it engine_pod_name -n matrixx -- bash --login -c
"print_engine_stats.py"
Results
version - 5083
time - Mon 2019-01-28T16:50:36
----------------------------------------------------------------
Error Stats
-----------
|Blade FqId| Blade Role| Errors|Critical Errors
======|==========|=============|=======|===============
max| 1:1:1| processing| 0| 0
| 1:1:2| processing| 0| 0
| 1:1:3| processing| 0| 0
| 1:2:1| publishing| 0| 0
| 1:2:2| publishing| 0| 0
min| 1:3:1|checkpointing| 0| 0
total| | | 0| 0
avg| | | 0.0| 0.0
Charging Server Stats
---------------------
|Blade FqId| Blade Role|Average Latency (us)
======|==========|=============|====================
max| 1:1:3| processing| 3584
| 1:1:2| processing| 3572
| 1:1:1| processing| 3510
| 1:2:1| publishing| 0
| 1:2:2| publishing| 0
min| 1:3:1|checkpointing| 0
total| | | 10666
avg| | | 3555.333
*Col "Average Latency (us)" total and avg only include proc blade types.
Database Memory Stats
---------------------
| | | Total Memory (KB)
|Blade FqId| Blade Role| Used| Free
======|==========|=============|===========|===========
max| 1:1:3| processing| 2566917| 4285063
| 1:1:2| processing| 2563853| 4265595
| 1:1:1| processing| 2559442| 4274576
| 1:2:1| publishing| 2550486| 4292827
| 1:2:2| publishing| 2550486| 4292827
min| 1:3:1|checkpointing| 2550486| 4292827
total| | | 15341670| 25703715
avg| | | 2556945.0| 4283952.5
Diameter Gateway Stats
----------------------
|Blade FqId| Blade Role|Average Response Time (us)
======|==========|=============|==========================
max| 1:1:1| processing| 4264
| 1:1:2| processing| 4222
| 1:1:3| processing| 4221
| 1:2:1| publishing| 0
| 1:2:2| publishing| 0
min| 1:3:1|checkpointing| 0
total| | | 12707
avg| | | 4235.667
*Col "Average Response Time (us)" total and avg only include proc blade types.
MDC Gateway Stats
-----------------
|Blade FqId| Blade Role|Average Latency (us)
======|==========|=============|====================
max| 1:1:1| processing| 795
| 1:1:3| processing| 694
| 1:1:2| processing| 688
| 1:2:2| publishing| 637
| 1:2:1| publishing| 0
min| 1:3:1|checkpointing| 0
total| | | 2177
avg| | | 725.667
*Col "Average Latency (us)" total and avg only include proc blade types.
Database OID Index Memory Stat
------------------------------
|Blade FqId| Blade Role|Total Index Buffer Allocated Size (KB)
======|==========|=============|======================================
max| 1:2:1| publishing| 651343.500
| 1:1:1| processing| 321063.188
| 1:1:2| processing| 321063.188
| 1:1:3| processing| 321063.188
| 1:2:2| publishing| 321063.188
min| 1:3:1|checkpointing| 321063.188
total| | | 2256659.438
avg| | | 376109.906
Other Stats
-----------
|Blade FqId| Blade Role|Transactions Per Second
======|==========|=============|=======================
max| 1:1:3| processing| 1488
| 1:1:2| processing| 1477
| 1:1:1| processing| 1461
| 1:2:1| publishing| 0
| 1:2:2| publishing| 0
min| 1:3:1|checkpointing| 0
total| | | 4426
avg| | | 1475.333
*Col "Transactions Per Second" total and avg only include proc blade types.
Sys Stats
---------
| | | Cpu Utilization (%) | Shared Memory (MB) | Swap Memory Usage (MB) | Physical Memory Usage (MB)
|Blade FqId| Blade Role| iowait| sys| idle| usr| total| used| total| used| cached| free| free| total| cached| available
======|==========|=============|==========|=========|==========|=========|============|============|==========|========|==========|==========|============|============|==============|==============
max| 1:1:2| processing| 0.01| 1.78| 86.44| 11.41| 100000| 12349| 4095| 0| 0| 4095| 101234| 257651| 143146| 139138
| 1:2:1| publishing| 0.04| 1.51| 87.22| 11.09| 100000| 12672| 4095| 0| 0| 4095| 147899| 257651| 101041| 147427
| 1:1:3| processing| 0.02| 1.51| 87.33| 10.97| 100000| 12349| 4095| 0| 0| 4095| 111453| 257651| 134206| 142849
| 1:1:1| processing| 0.02| 1.85| 87.0| 10.66| 100000| 12349| 4095| 0| 0| 4095| 106154| 257651| 138593| 139392
| 1:3:1|checkpointing| 0.0| 0.64| 90.76| 8.59| 100000| 12349| 4095| 0| 0| 4095| 129881| 257651| 118127| 143329
min| 1:2:2| publishing| 0.0| 1.14| 93.29| 5.44| 100000| 12349| 4095| 0| 0| 4095| 148489| 257651| 100600| 147783
total| | | | | | | 600000| 74417| 24570| 0| 0| 24570| 745110| 1545906| 735713| 859918
avg| | | 0.015| 1.405| 88.673| 9.693| 100000.0| 12402.833| 4095.0| 0.0| 0.0| 4095.0| 124185.0| 257651.0| 122618.833| 143319.667
Each
Transactions Per Second (TPS) number represents the total TPS processed by the MATRIXX Engine. See the following
examples.Transaction Processing Stats
This example shows the other statistics:
Other Stats
-----------
|Blade FqId| Blade Role|Transactions Per Second
======|==========|=============|=======================
max| 1:2:2| publishing| 6661
| 1:2:1| publishing| 6212
| 1:1:1| processing| 6120
| 1:1:2| processing| 6115
| 1:1:3| processing| 6114
The TPS for each server is about 6000.
The following example shows transaction (Txn) statistics for transaction processing:
Txn Stats
---------
Parallel Business Current Maximum Total Average Maximum Effective
Commit Collision Txn Txn Message Msg Size Msg Size Txn Count
Count Count Count Count Count in Bytes in Bytes Per Second
=========================================================================================
0 0 64 62044 8208709 820 869 6122