Mobile app Performance Test metrics

Performance testing plays an important role in the application quality assurance, which is summed up in three aspects: application testing on client performance, application of performance testing on the network, and application of performance testing on the server side. Generally, the three effective and reasonable combination can achieve a comprehensive analysis of the system performance and bottleneck prediction.

Through the performance test tools to obtain the performance of the test object, the performance indicators and the industry standard values or competitor values to do a comparison, to obtain a comprehensive conclusion and optimization of the improvement Program. The following is an example of a typical app such as a hand tour for a detailed description of the client performance metrics.

Inclusion

Package size can be listed as performance indicators, from the app performance indicators and game operation two dimensions, players are more likely to be small package and performance, and sometimes they will be a cross-trade relationship.

CPU Usage

In general, with the mainstream mobile phone play game 20%-40% CPU occupancy is reasonable, of course, this value with the recent years of mobile phone hardware configuration, will be slightly reduced, if the CPU occupancy rate of more than 80% is very worthy of our attention.

Number of frames (FPS)

Renders that can be used to indicate whether the page is smooth. Mobile game frame rate fps,30-60 are acceptable, on the 60 for the human eye subjective feeling difference is not much. For game development, not a higher FPS must be better, FPS depends on the video card, followed by memory, CPU, and then the network. Therefore, the comprehensive game other performance indicators, select a suitable FPS can be.

Memory usage

In Android, each app process, in addition to sharing dirty with other processes, uses private memory (private dirty), usually using PSS (= private memory + proportional allocation of shared memory) to measure the memory overhead of an app. The memory resources of the mobile device are very limited, and the private memory allocated for each app process is limited. On the one hand, we should reasonably apply for memory use, so as not to cause frequent GC (garbage collection mechanism) impact performance and large object application memory overflow; On the other hand, we need to release memory in time to avoid a memory leak.

Electricity

Mobile devices have very limited battery power relative to the PC, which is especially important to maintain long-lasting endurance. In addition, many features of Android are more power consumption (such as screen, Gps,sensor sensor, wake-up mechanism, CPU, network, etc.), we must carefully check the use of the app's electricity, so as to avoid the user's mobile phone consumption of heat, resulting in bad experience.

Flow

The current network type contains 2g\3g\4g\wifi, there are different operators, we often encountered in the use of the application of large resources, repeated requests, call response slow, call failure and other situations. Under different network types, we not only have to control traffic usage, we also need to speed up the response of the request. In addition, for the need of online hand-tour, some games for different networking types of network use different traffic consumption strategy, mainly divided into WiFi environment and cellular network environment. So for different games, when we count traffic consumption, we may want to connect to different networks for testing.

For mobile app testing, compared to app compatibility testing, App function testing, performance testing is more of a test application on the terminal hardware operation, but performance testing is not a separate, and many of the time is to test with other special tests.

Testbird

Mobile app Performance Test metrics