Performance insight is a powerful tool that focuses on database performance tuning, load monitoring and correlation analysis. It uses intuitive and simple ways to quickly evaluate the database load, find the source of performance problems and the corresponding SQL statements, so as to guide you when, where and what actions to take for data performance optimization.
Performance testing, what on earth are you going to test?
Some are similar to the requirements analysis in the development process, and the common test performance insights indicators are as follows.
Response time.
Response time refers to the time taken by a request or operation from sending to receiving feedback, including application server (client) processing time, network transmission time, and database server processing time.
As far as the user is concerned, how long it takes to click on the query on the page to get the result, this is the response time.
Users don't care how many services your backend has gone through, slow is the original sin.
For micro-service systems, link monitoring is more important. It can help us quickly locate where we are slow.
TPS/QPS.
TPS (Transaction Per Second) is the number of transactions processed by the system per unit time (per second).
I think there are a lot of similar concepts online: clicks / clicks, throughput / throughput, PV/UV, which I won't repeat here.
Personally, it seems that TPS/QPS is essentially to test the limits of your application, when the traffic is large, can the program survive?
There are two main concepts involved here: high performance and high availability.
Test preparation.
Once the test indicators are defined, you need to prepare for the test.
Environment preparation: for example, if you want to test the database, you need to prepare the database resources corresponding to the configuration.
Preparation of script: data initialization script, calling script, etc.
This can be compared to code development in the development process.
Ps: performance stress testing is generally not very common, so the environment preparation process is relatively long, which needs to be noted.
Test report.
After the test, be sure to give a report of the test results.
Whether to pass the pressure test requirements?
What is the highest QPS?
In this way, the developer can optimize accordingly according to this report.