Android performance analysis tools finishing

Link to the original text : http://www.jianshu.com/p/8b77d394b2a6 Android

performance analysis tools summary With functional UI rendering detection function (open Settings, then go to Developer Options -> Debug GPU Overdraw, select Show overdraw areas, set the Chinese child paper in the mobile phone system, and translate it by yourself) Function: used to detect the number of redraws of the UI, develop can be used to optimize the performance of the UI. Experience: a sharp tool for detecting UI performance, which is very helpful for developers to optimize UI. Because a large number of redraws can easily cause the app to freeze or directly cause frame loss. Developers who are familiar with the drawing principle of View can optimize some layouts or custom controls accordingly. For example, using the layout_weight setting of an item in a ListView or GridView will cause redundant redrawing. There are many other situations, not to mention one by one. As for how to use it, you can use Google Profile GPU Rendering type: the system has its own function UI rendering detection function (open Settings, then go to Developer Options -> Profile GPU Rendering. Select On screen as bars) Function: used to detect the rate of UI drawing frames and time-consuming, the same developers can use to optimize the performance of the UI. Experience: Similar to the Debug GPU Overdraw function, but it reflects the rate at which the UI draws frames. It can also be used to detect whether your app is dropping frames or overdrawing. The specific operation can be Googled by yourself.












Hierarchy Viewer
type: SDK comes with tools (open Settings, then go to Developer Options -> Profile GPU Rendering. Select On screen as bars)
Function: Detect UI rendering
Use experience: old tools, Google

Memory Monitor, Heap Viewer, Allocation Tracker
Type: AndroidStudio's own tool
Function : Both are tools for memory detection and analysis
Use experience: Needless to say, everyone knows...

Memory Analyzer Tool (MAT)
Type: ADT era plug-in, also has an independent MAT version Function
: The artifact of detailed memory analysis!
Experience: It is the only good memory I have under ADT. AS's current tools are inferior to it. I hope to keep up with it soon. In order to solemnly introduce my beloved, I decisively present its official documentation: http://help.eclipse.org/mars/index.jsp

Traceview, Systrace
Type: SDK
comes with Function: A tool for CPU usage analysis
Use experience: Exclude CPU performance A powerful tool for bottlenecks, TraceView can let me know the CPU time of each function call, as well as the total CPU time, etc., which is convenient for troubleshooting and optimization. Systrace can let me know the usage of each AP sub-module, which is also helpful for bottleneck investigation, performance optimization, etc. In short, it is very good.

Battery Historian
Type: Independent open source software (recommended tool at the Google IO conference)
Function: Power consumption analysis
tool Experience: What Google personally pushed in power consumption analysis Needless to say, the basic use of Battery Historian 1.0 is quite a lot on the Internet, you can Check it out for yourself. The function of 2.0 is more perfect, but the domestic data is less, and the foreign data is OK. There are two points to pay attention to when using Battery Historian, one is that it only takes effect on systems 5.x and above, and the other is to use Python2.x when building the environment, not Python3.x. Because the syntax changes of the two versions are very large, Battery Historian will report an error under Python 3.x. Finally, this is an open source project https://github.com/google/battery-historian

------------------------------- ----Separation line-----------------------------------

The above are mainly official tools, the following It is some third-party apk tools...

WakeLock Detector
function introduction: It can detect and record the running state of the mobile phone, and can count which applications trigger the CPU operation to consume CPU, and which applications trigger the screen to light up. At the same time, you can also perform statistics on the running time, and you can view the details of in-app usage.

Experience: I made an app before and was complained by users that it consumes too much power. Found it by accident and used it as a battery drain test. At the same time, it can also count the power consumption of other apps installed on the mobile phone, which is convenient for making comparisons and aligning with the top-level experience apps.

Prerequisites for use: The mobile phone needs to be rooted, and the app needs to obtain the root permission

. GSam Battery Monitor
Function Introduction: Detect the consumption of the battery power of the mobile phone, and can use the line graph for statistical display.

Experience: It is a good product. It can calculate which part of the phone's power is consumed by your power, which can be traced back to which apps are using this part of the function, so as to locate the culprit of the phone's excessive power consumption.

Prerequisites for use: The mobile phone needs to be rooted, and the app needs to obtain root privileges

Trepn Profiler
Function Introduction: Produced by Qualcomm, I like it! Analysis and detection of mobile phone CPU consumption, and can analyze a specific app.

Experience: It is used to debug and analyze your own app, and a line graph is used to display the CPU consumption of the app in real time.

Prerequisites for use: The mobile phone needs to be rooted, the app needs to obtain root permissions, and only the CPU of the mobile phone is supported by Qualcomm.

Root Explorer
function introduction: a file browser that can view the unencrypted database of the app, read the data in it, and support simple conditional queries.

Experience: When developing, you need to confirm whether the data is successfully inserted into the database. With it, you can directly open the database file to browse and search.

Prerequisites for use: The phone needs to be rooted, and the app needs to obtain root permissions

-----------------------------------Separation line -----------------------------------

In addition to the above apk tools, finally developed by some well-known IT companies Tools (including SDK), very easy to use...

Bugly
pull BUG, ​​pull ANR SDK. The stuff produced by Tencent is great. For the released products, you want to accurately locate various bugs that crash, and use it to be accurate. And the update frequency of bugly is quite fast, the efficiency of large companies is really willful (it can only be said that goose factories are more and more able to use technology to make money~)

Official website address: http://bugly.qq.com/

BugTags
official website said: Testing has never been easier! A new generation of defect discovery and management tools designed for mobile testing. Personally think it is very good, also recommend!

Official website address: https://bugtags.com/

GT
This artifact may not be known to many people (I guess). Tencent MIG special test team developed a cool and cool artifact, as long as there are many gods, not much to say, go directly to the official website to see, I have already cried (Tencent's technology is really good)

Official website address: http:/ /gt.tencent.com/index.html

iTest
is a test tool produced by iTest, which can be installed and used directly. It is a professional mobile phone automatic performance monitoring tool for Android testers.

Official website address: http://itest.iflytesting.com/?p=1 The test tool produced by

Emmagee NetEase is similar to iTest. The biggest advantage is that it can detect the common performance indicators of the application and save it in csv format for convenience
Check the parameters of the application. The test results look more intuitive, and a very important point is that it is open source!!!!

Official website address: https://github.com/NetEase/Emmagee

to be continued...
That's all for now, there will be better follow-up The tools will also be updated. Some tools are outdated and will be removed here. The

article is archived here: https://github.com/D-clock/Doc