This document discusses performance testing tools for Android applications, including Trace View for analyzing execution logs to find issues, instruction counting to measure performance, and heap dump analysis to diagnose memory-related bugs. It provides instructions for starting and stopping method tracing with Trace View, pulling trace files from devices, viewing heap dumps, and converting hprof files to a format readable by analysis tools. The goal is to help developers test and optimize the speed and memory usage of their Android applications.

1. Android: Performance Testing -Akshay Dashrath

2. Need Speed?

3. What about?

4. Tools Analysing logs (Trace View) Heap Dump Analysis Debug class

5. Trace View Graphical Tool to analyse execution logs

6. // start tracing to "/sdcard/test.trace" Debug.startMethodTracing(“test"); // ... // stop tracing Debug.stopMethodTracing(); adb pull /sdcard/test.trace C:/ traceview C:/trace.test

8. Issues If a thread exits during profiling, the thread name is not emitted; The VM reuses thread IDs. If a thread stops and another starts, they may get the same ID. .trace files larger than 8MB cannot be read by the Viewer

9. Instruction Count

10. Heap Dumps C:/adb shell C:/ chmod 777 /data/misc – In order to make the /data/misc directory writeable C:/exit C:/ adb shell ps C:/ adb shell kill -10 1234 -------Example C:/ adb pull /data/misc/heap-dump-tm-pid.hprofaddress.hprof C:/ hprof-conv heap-dump-tm-pid.hprof4mat.hprof

13. Questions?