This document discusses various tools and techniques for optimizing Android app performance. It describes tools in Android Studio like Lint, DDMS, Developer Options, Hierarchy Viewer and Systrace that can help detect and fix issues like memory leaks, GPU overdraw and inefficient code. It also provides code snippets and tips to write optimized code through best practices like using static final for constants and avoiding unnecessary object creation. The goal is to analyze, improve and smooth out an app's performance through optimization.

2. Code level
fixes
DDMS tools
&
Developer
Options
GPU overdraw
Heap dump
Allocation Tracker
Hierarchy Viewer
GPU Rendering
Trace Viewer
Optimized Imports
Performance tweaks
Lint Tool
Avoid memory leaks
Improve
Code
Analyse &
improve app
performance
Smooth,
Optimized
app
Optimization

3. Avoid Memory leaks
❖ Use Drawables efficiently
❖ Broadcast
❖ Context related leaks
● Application level context
● Activity level context

4. Performance Tweaks
❖ Use Static Final to declare Constants.
❖ Access variables directly instead of getter/setter for internal
use.
❖ Avoid Creating Unnecessary Objects.
❖ Use loops efficiently.

5. For Loop
Code Snippet
Log.i(TAG, "-------------------------------------------------");
Log.i(TAG, "-------Start: FOR loop one");
for (int j = 0; j < mCountList.size(); j++) {
//stuff
}
Log.i(TAG, "-------End: FOR loop one");
Log.i(TAG, "-------Start: FOR loop two");
int count = mCountList.size();
for (int j = 0; j < count; j++) {
//stuff
}
Log.i(TAG, "-------End: FOR loop two");
Log.i(TAG, "-------------------------------------------------");

6. Logcat

7. Lint Tool
❖ Static code analysis tool that checks your Android project
source files for potential bugs and optimization improvements
for correctness, security, performance, usability, accessibility,
and internationalization.

8. Lint Result
To run Lint tool Analyze Inspect Code

9. DDMS & Developers Options
❖ GPU overdraw
❖ GPU Rendering
❖ Trace Viewer
❖ Hierarchy Viewer
❖ Heap dump
❖ Allocation Tracker

10. GPU Overdraw
Atleast 4X
3X
2X
1X
Debug GPU overdraw:
Lets you see when and where this is happening so
you know if it is a problem.

11. Buggy Without Overdraw Issue
Example of GPU overdraw

12. Profile GPU rendering
❖ Blue bar represents the time used
to create and update the View's
display lists.
❖ Red bar represents the time
spent by Android's 2D renderer
issuing commands to OpenGL to
draw and redraw display lists.
❖ Orange bar represents the time
CPU is waiting for the GPU to
finish its work.

13. Hierarchy Viewer tool
❖ Allows you to debug and optimize your user interface.
❖ It provides a visual representation of the layout's View hierarchy
(the Layout View) and a magnified inspector of the display (the
Pixel Perfect View).

14. Systrace tool
❖ It shows where time and CPU cycles are being spent,
displaying what each thread and process is doing at any given
time.

15. Heap Option
❖ To get a little information about what kind of memory your
application is using and when, you can view real-time updates
to your app's heap in the Device Monitor.

16. Allocation Tracker
❖ Allocation Tracker records an app's memory allocations and
lists all allocated objects for the profiling cycle with their call
stack, size, and allocating code.
❖ Identifying where many similar object types, from roughly
the same call stack, are allocated and deallocated over a very
short period of time.
❖ Finding the places in your code that may contribute to
inefficient memory use.

17. Source
❖ http://developer.android.com/tools/help/index.html
❖ http://android-developers.blogspot.in/