1. General analysis ideas
Observation phenomenon -- > Progressive layer by layer -- > Narrow the scope -- > Reasoning analysis -- > Continual verification -- > Confirm the conclusion
Observation Phenomenon: Phenomenon only refers to page performance, server resource performance, health of various middleware, log logs,
Parameters of various software, health of various databases, etc.
Common indicators that need attention: response time, TPS , QPS , success rate, CPU , MEMORY , IO , number of connections, number of processes \ threads, cache hit rate, traffic, etc.;
In addition to public indicators, there are also some indicators that need to be monitored for specific system software. For example, the recycling situation of each memory generation in the JVM and the GC situation, max active processes and slow requests in PHP-FPM , etc.
Layer-by- layer progression: According to the analysis and exclusion of the system layer by layer, start from the application server layer, check layer by layer, and finally analyze the database layer.
Narrowing the scope: After going through the layers, the scope of exclusion and analysis is narrowed.
Reasoning analysis: It is necessary to adhere to the principles of bold guessing and careful verification.
Continuous verification: If we do not have enough experience, it is difficult to be precise when analyzing, and patient and continuous verification is our only method.
Determine the conclusion: practice more and summarize more
A typical three-tier architecture model:
Client——web server ——DB server
2. Test report writing skills
1) The structure is clear, and there must be a good sense of hierarchy, so that it does not look chaotic.
2) The description is concise, do not use too much nonsense;
3) Mixed pictures and texts, a picture is worth a thousand words, if you can use a picture to explain it clearly, you don’t need a paragraph;
4) Data comparison, data and comparison are more convincing
Also, write different reports for different people. For leaders, try to avoid technical jargon and use easier-to-understand words to describe them. If it is sent to a technician, it can be written from a professional technical point of view, reflecting the analysis process, details, solutions and conclusions.
Appropriate solutions should be given to the analyzed problems.