forked from codepath/android_guides
-
Notifications
You must be signed in to change notification settings - Fork 0
Debugging and Profiling Apps
Nathan Esquenazi edited this page Feb 2, 2016
·
13 revisions
(Needs Attention)
-
Analyzing Display and Performance (
systrace) -
Optimizing your View and Inspecting Hierarchy (
hierarchyviewer) -
Investigating your RAM Usage (
monitor) -
Profiling with Traceview (
traceview) - Profiling Android Apps - Performance Turning
- Vogella Android Analysis Tools
- Performance Course on Udacity
- Performance Doc from Udacity
In addition, the following concepts need to be included:
- Profiling GPU Rendering - quick visual representation of how much time it takes to render the frames of a UI window relative to the 16-ms-per-frame benchmark.
- Visualizing Overdraw - Shows on the device where an app might be doing more rendering work than necessary. Helping you see where you might be able to reduce rendering overhead.
- Heap Viewer - Identifying memory leaks
- LeakCanary for finding memory leaks easily
- Allocation Tracker - Finding the places in your code that may contribute to memory trashing.
- Batterystats - Shows where and how processes are drawing current from the battery.
- Batteryhistorian - Visualize system and application level events on a timeline. Guide to getting started
Check out the following links regarding optimizing performance:
Created by CodePath with much help from the community.