Android Client Performance parameter monitoring

Background:

When doing Android client testing, it is sometimes necessary to monitor cpu/mem/power consumption/interface load time/traffic and so on. So we went up and down, netizens told me two programs: Anothermonitor and Emmagee, before, I wrote a tool, below on these several programs to do a comparison and description.

Anothermonitor and Emmagee are all in the form of APK, the following is the official website:

https://code.google.com/p/anothermonitor/

Https://github.com/NetEase/Emmagee

Look at the introduction:

Anothermonitor is a application for Android which monitors and records thememory and CPU usage values of the mob Ile phone. Thus, the program is intendedfor anyone whom would being interested in knowing the mobile resources state.

001.png

emmagee Function Description:

1. Detecting CPU usage and overall CPU usage for the current time tested application

2. Detecting the amount of memory occupied by the application under test at the current time, as well as the percentage of total Ram occupied, the remaining amount

3. Detect the amount of traffic consumed by the application from start to current time

4. Test data is written to the CSV file and stored in the phone

5, can choose to open the floating window function, floating window real-time display of the measured application occupancy performance data information

6, in the floating window can quickly start or turn off the phone's WiFi network

002.png

Two tools more similar function, the latter one more traffic monitoring, the advantage is only need to install to the Android phone can be used, the disadvantage is that the program itself on the mobile phone resources are also affected, monitoring content is not rich enough.

I wrote a tool of my own, the collection of resource parameters, mainly rely on the phone's own command line.

The main use of the command: Getprop and Dumpsys

List of documents:

L Getdatav1.bat

L Getdatav2.bat

L android log analysis. xls

L Wireless ADB connects Android phones and computers. docx

Description

The first version is a USB cable connected to the PC and mobile phone, when the phone root installed after the BusyBox, so all kinds of commands are complete, so getdatav1.sh you will find all Linux commands;

Second version: Since most phones will not install BusyBox, there is no awk,sed class of commands, so getdatav1.sh modified to getdatav2.sh, the previous awk, SED and other commands are no longer used, using DOS batch processing for text processing.

The process of running the program is to run getdata.sh, the file has detailed usage instructions, generate a lot of collected data files, and then open the Excel file, click Generate, the previous batch collected data files loaded into an Excel file, and generate a chart.

In the test process found that the USB cable connection to the PC, will cause the phone has been charging, so there is a wireless solution, to ensure the accurate power consumption.

May be able to support Monkeyrunner run for several hours, the number of crash and log are generated together into the report. This is more practical. Do it when you are free.

Download Link:

http://download.csdn.net/detail/testingba/7716309