1, the user concurrency test
User concurrent test is the most important part of the performance test, including the process of load testing and stress testing. Mainly to gradually increase the number of users to increase the burden on the system until the point of performance bottleneck or can not receive. To test the general situation normal number of concurrent users and lower limits of the number of concurrent users.
Concurrent user test is the core function of the system and to test important business to business to real data as input, select a representative and critical business operations designed test cases. The main use cases written in the following two aspects:
Test core modules: the core function modules concurrent user testing, to test whether the system stable operation.
For example, a public Internet mail system, around 9:00 every morning may be the peak of mail, after which time thousands of users have to enter the mail system at work, this time the system needs to receive and send large amounts of mail. So the mail system function modules to be tested concurrently. Pass the test can tell if a database server, operating system, network equipment able to withstand the test, and can analyze the bottleneck.
Table 2 lists to some common parameters (data tables for test cases and test results of example), can be increased according to actual needs and deleted, the disk I / O, database-related test parameters to be selected according to the actual situation, and therefore not listed.
| Features |
When online users peaked, regular mail to send and receive normal to ensure that within 200 users can simultaneously access the mail system can normally send and receive mail. |
||||||||
| purpose |
200 users simultaneously online within the test system can properly send messages. |
||||||||
| method |
Using LoadRunner recording tool to record a mail sending process, and then use it to complete the test, you want to monitor the performance of the database server and web server. In which ordinary mail sent to e-mail, attachments no larger than 1M. |
||||||||
| Number of concurrent users and transaction performance |
|||||||||
| Number of concurrent users |
The average transaction response time |
Transaction maximum response time |
The average number of transactions processed per second |
Transaction success rate |
Hits per second |
The average flow rate (bytes / sec) |
|||
| 100 |
1.344 |
2.078 |
5 |
100% |
102 |
5177 |
|||
| … |
… |
… |
… |
… |
… |
… |
|||
| Number of concurrent users and database host |
|||||||||
| Number of concurrent users |
CPU utilization |
MEM utilization |
Disk I / O parameters |
DB parameter 1 |
Other parameters |
||||
| 100 |
23％ |
11％ |
… |
… |
… |
||||
| … |
… |
… |
… |
||||||
| Table of concurrent users and application servers |
|||||||||
| Number of concurrent users |
CPU utilization |
MEM utilization |
Disk I / O parameters |
||||||
| 100 |
32％ |
27％ |
… |
||||||
| … |
… |
… |
… |
||||||
Table 2 Performance test of the core module
In the preparation of such use cases, to conduct a comprehensive analysis of selected systems of the various core modules, design test cases for each module: The module is divided into small "transaction" test, it is easy to locate the problem in the test analysis what appears where. E.g. messaging system may be divided into: received mail, sending mail, open the mail small transactions to write tests, each operation is performed as a use case.
2, network performance testing
Network performance test is to show people the exact bandwidth, delay, load change and how it affects the port user response time. In the actual software projects, mainly to test the relationship between the number of users and network bandwidth.
Written in the format example of Table 3 (as an example of the data in the table data):
| purpose |
Test system operation network usage at different conditions of concurrent users |
||
| method |
(E.g., 256K) used in different WAN bandwidth associated transaction operation script LoadRunner record a message system for testing a different number of concurrent users, records various user connections, the performance variation of different concurrent requests; simultaneously recorded router ports traffic and other data. |
||
| operation hours |
10 hours |
||
| The number of concurrent users |
The average transaction response time |
Server port traffic |
Packet loss rate |
| 100 |
2.816 |
50.2M/S |
0.001% |
| 500 |
3.876 |
98.2M/S |
0.002% |
| … |
… |
… |
… |
Table 3 Network Performance Test
This portion may be independently tested, and the user may be concurrent performance testing, fatigue strength and large amount of data performance testing combined use of tools to adjust the basis of the original network settings, so as to achieve the purpose of monitoring network performance. Network performance tools are usually employed to evaluate the performance, integration is performed by a system engineer.