Measuring the potential overhead of PMM Client on MySQL workloads
Having good historial metrics monitoring in place is critical for properly operating, maintaining and troubleshooting database systems, and
Percona Monitoring and Management is one of the options we recommend to our clients for this. One common concern among potential users is how using this may impact their database's performance. As I could not find any conclusive information about this, I set out to do some basic tests and this post shows my results. To begin, let me describe my setup. I used the following Google Cloud instances:
- One 4 vCPU instance for the MySQL server
- One 2 vCPU instance for the sysbench client
- One 1 vCPU instance for the PMM server
PMM | SSL | tps (p99) |
enabled | enabled | 1167.518 |
enabled | disabled | 1397.397 |
disabled | disabled | 1429.097 |