Software Performance Testing base part 3

Performance testing process

Test execution

  1. Set up a test environment
  2. Deployment of test environments
  3. Perform a test environment
  4. Test indicators monitoring

Result Analysis Report

Definition: Analysis of test results, test locate the problem, test report output

  1. Performance Compliance Verification : View the test results meets the requirements, such as response time, resource utilization, throughput, etc.

  2. The performance of proficiency testing : test to see whether the results meet the requirements, the performance curve recording software system

  3. For determining whether a performance bottleneck : first determines whether there is a hardware (including network) bottlenecks, if a hardware bottleneck, then the order of the system software (application servers, database servers, operating systems) were analyzed in accordance with the application software, identify bottlenecks point
    tuning: verified by the performance capabilities of performance bottlenecks analysis

    *硬件瓶颈分析方法(windows—) perfmon
    内存分析方法
    处理器分析方法
    磁盘I/O分析方法 	软件瓶颈分析方法*
    

Software bottleneck analysis : Analyze transaction response time, throughput, determine whether there are performance problems, performance issues if found, then find out the response time does not meet the requirements or more failed transaction occurs, its decomposition, and then be web page breakdown, in order to determine the effect of the elements of performance.
Performance Monitoring System under https://www.cnblogs.com/fanpl/articles/8762947.html linux

  1. Test Report
    Test Indicators : description and test scenarios corresponding to the average response time of the transaction, the transaction information throughput, resource consumption indicators, the number of users running.
    Results and summary : According to the test target, describing the results of the final analysis obtained, and the corresponding recommendations.
    Test Case Report

Acceptance Test

To the customer, the customer validation test software, will generally take the core business, and randomness of a simple test procedure

Performance requirements

Recessive performance requirements

Performance requirements are often hidden by the proposed common type of customers

Dominant performance requirements

Dominant performance requirements are generally made by professional customers, such customers often have their own development department and test teams

Performance requirements elicitation method

Based on the user explicitly asks

Test-related data and indicators based on the user explicitly gives the analysis of system performance needs of the most direct and most convenient way

Based on existing data analysis results to provide users with finishing

Existing paper-based data refers to data such as customer business transactions

Similar projects based on the same industry or similar industry data

When he did some resources, we must learn to help themselves outside forces to help achieve the goal of obtaining performance

80/20 principle analysis calculated

For example:
a company's annual business volume concentrated in 8 months, 20 days a month, working eight hours each working day.
The company processing business each year the number of about 100 million transactions, of which 15% of the business processes of each business to be submitted seven requests to the application server; 70% of the business processes of each business to be submitted five requests for application servers; the remaining 15 every business needs to submit a request to the application server 3 percent of the business process. Taking into account the needs of the next three years of business development, testing basis having twice the current volume of business.
The total number of requests is:
(+ X7% 100x15 100x70 100x15%% + X5 X3) X2 = 1000 million times / year
requests per day number: 1000/160 = 62500 / day
of requests per second as: (62500x80%) /(8x20%x3600)=8.68 times / sec
is not in principle 2-8:
62500 / (8x3600) = 62500/28800 = 2.7 times / second

Three performance

The client application performance testing

Applications on the network performance test

Application performance test on the server side

Published 17 original articles · won praise 9 · views 1711

Guess you like

Origin blog.csdn.net/potato_yaya_/article/details/101013926