Tuning performance testing needs to identify bottlenecks, bottlenecks in the system which would generally exist:
Hardware performance bottlenecks on :
Generally refers to the problem of CPU, memory, disk I / O area, divided into server hardware bottlenecks, network bottlenecks (on the LAN can not be considered), server operating system bottlenecks (parameter configuration), middleware bottlenecks (parameter configuration, database, web servers, etc.).
Performance bottlenecks on application software:
Generally it refers to an application server, web server, etc. applications, further comprising a database system.
For example: JDBC connection pool parameters weblogic middleware platform configured unreasonable, the bottlenecks.
Performance bottlenecks on the application:
Generally it refers to developers of new developed applications (SQL statements, database design, business logic, algorithms, etc.)
For example, program planning and inadequate infrastructure, program design itself there is a problem (serial processing, the request processing thread is not enough), resulting in lower system performance when a large number of users to access and create bottlenecks.
Performance bottlenecks on the operating system:
Generally refers windows, UNIX, Linux and other operating systems. For example, during performance testing, there is insufficient physical memory, virtual memory settings is also unreasonable, virtual memory exchange efficiency will be greatly reduced, resulting in a greatly increased response time behavior, then consider the performance bottleneck on the operating system.
Performance bottlenecks on the network device:
Generally it refers to a firewall, dynamic load balancing, switches and other equipment. For example, on setting up dynamic load balancing mechanism to distribute dynamic loads, when the discovery of hardware resources on an application server has reached the limit, the dynamic load balancer subsequent transaction request is sent to the other application server load lighter . When testing found that dynamic load balancing does not play a relevant role, then we can think network bottlenecks.
The reason appears and positioning performance testing is very complicated, here is a brief introduction of several common bottlenecks types and features, and performance testing is needed is a comprehensive consideration of factors depending on various circumstances, and help developers \ DBA \ operation and maintenance personnel locating performance bottlenecks together.
When looking for bottlenecks in the following order, from easy to difficult
Server hardware bottlenecks -> network bottlenecks -> server operating system bottlenecks (Parameters configuration) -> middleware bottlenecks (parameter configuration) -> application bottlenecks (SQL statements, database design, business logic, algorithms, etc.)