Shulou(Shulou.com)06/03 Report--

1. General analysis idea

Observe the phenomenon-- > step by step-- > narrow the scope-- > reasoning analysis-- > constantly verify-- > confirm the conclusion.

Observe phenomena: phenomena only refer to the performance of the page, the resource performance of the server, the health of all kinds of middleware, log logs,

The parameters of all kinds of software, the health degree of all kinds of databases, etc.

Common metrics to pay attention to: response time, TPS, QPS, success rate, CPU, MEMORY, IO, number of connections, processes / threads, cache hit rate, traffic, etc.

In addition to public indicators, there are some indicators that need to be monitored for specific system software. For example, the recycling of memory generations in JVM and the situation of GC, max active processes, slow requests in PHP-FPM, etc.

Progressive layer by layer: according to the analysis and exclusion of the system layer by layer, start from the application server layer, check layer by layer, and eventually analyze to the database layer.

Narrow the scope: after layers of progress, the scope of exclusion and analysis is narrowed.

Reasoning analysis: it is necessary to adhere to the principle of bold guess and careful verification.

Continuous verification: if we do not have enough experience, it is difficult to hit the nail on the head in the analysis, patient constant verification is our only way.

Determine the conclusion: practice more and sum up more

A typical three-tier architecture model:

Client--web server-DB server

two。 Writing skills of test report

1) the structure is clear and should have a good sense of hierarchy, so that it will not look messy.

2) succinct description, don't talk too much nonsense

3) mixing pictures and texts, a picture is worth a thousand words. If you can explain clearly with a picture, you don't need a paragraph.

4) data comparison, there is data, there is comparison, it is more persuasive

In addition, different reports should be written for different people. For leaders, try to avoid technical terms and describe them in words that are easier to understand. If you send it to a technician, you can write it from a professional technical point of view, reflecting the analysis process, details, solutions and conclusions.

For the problems analyzed, an appropriate solution should be given.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.