Software performance and performance testing

1. Software performance

IEEE (American Society of Electrical and Electronics Engineers) description of software performance
Software performance is the inherent characteristic of software, which is expressed as the time spent executing a function of the software.
? The description of software performance by national standards
GB/T16260 Software Engineering Product quality Part 1th: In the quality model, the quality of software is divided into 6 major features: functionality, reliability, ease of use, efficiency, maintainability, portability, and efficiency is the requirement for software performance. It is defined as: efficiency is the ability to provide the proper performance of a software product, relative to the amount of resources used, under prescribed conditions. Decomposition to three sub-attributes:
? Time characteristics: The ability to provide appropriate response and processing time as well as throughput rates when a software product performs its functions under defined conditions.
? Resource utilization: The ability of a software product to use the appropriate number and category of resources when performing its functions under prescribed conditions.
? Efficiency compliance: Software products follow the standards or conventions associated with efficiency.

Software performance is an indicator, is a non-functional feature of software, it is not concerned about whether the software can complete a specific function, but the response of the function of timeliness. Performance is a user's final feeling, mainly through response time, throughput, number of concurrent users, System resource occupancy, system stability of several indicators to measure.

2. Software Performance Testing
Through automated testing tools to simulate a variety of normal, peak and abnormal load conditions to test the performance of the system, to determine whether the system is defective, and based on the results to identify performance bottlenecks, improve system performance of the complete process. According to the performance test conducted by the field and performance test type two dimensions to see the performance test, divided as follows:
2.1 Test Field Division
? Performance verification: It can also be called defect discovery. By means of performance testing, we can find some defects such as concurrency anomalies in the system, and understand the concurrent processing ability and response time of products in a given environment. Routine performance tests are basically part of this area. such as the prototype validation during the unit phase, product performance validation during the release phase.
? Performance tuning: Improve system performance through performance testing, finding problems-tuning (tuning)-Testing (verifying tuning effects). such as the project on the feedback of the product performance issues of the special performance test.

? Competency verification: Verifies that the system has the capability to perform as expected (for typical scenarios, use cases) of the project itself under given conditions. Such as customer pre-launch acceptance test.
? Competency Planning: Understanding the scalability of system performance capabilities and performance capabilities in non-specific environments. The focus of attention is "how to make the system have the performance capabilities we require" or "how the system will have the capability to perform under certain conditions that may occur". For example, a project equipment selection test, verify that can meet the needs of the next 3-5 years of business development requirements of equipment configuration.

Software performance and performance testing