Android性能分析工具.ppt

Android Performance Profile Tools Jacky Cai – 2017/10/30 目录 Contents What is Jank? Android OS will send a VSYNC signal every 16ms and it will trigger UI Drawing. If UI Drawing can be finished in 16ms then we can get 60fps quality. While if an action needs take 24 ms to be done then when a VSYNC signal comes UI Drawing cannot be finished on time. It will cause a Jank. You will also see two same frames in 32ms. ( Different kinds of actions triggered in UI thread ) ( Jank caused by a long time Input Event ) Android OS requires to finish rendering a frame within 16ms. Human eyes cant recognize difference if faster than 60fps. Jank Causes Major Jank/Sluggishness Causes View Over Draw: The same pixel in screen was drawn more than 1 time while at last it can only show the last color. It wastes CPU/GPU resources. GC was triggered frequently and it blocks UI rendering. Dalvik VM: GC comsumes lots of resources, typically it takes 10-20 ms ART VM(after Android 4.4): GC takes only 2-3 ms. UI thread takes dozens of tasks and consumes lots of resources(e.g. IO, network, SQL operations), we should put them in a background thread. Android 5.0 introduced Render Thread and it takes GPU related tasks and reduced UI thread workload. Dozens of Apps are running in background and consume lots of resources. Sophisticated view Layout takes longer time to do measure/layout and increases CPU workload. Measure/layout actions are frequently triggered. Many animations are running at the same time. The Worst Jank/Sluggishness - ANR When App UI thread is blocked for too long, an Application Not Responding error is triggered. Activity Key Dispatch timeout - 5s Broadcast Receiver timeout - 10s (foreground)，60s (background) Service timeout - 20s Perf Tools TraceView Traceview provides a graphical UI for trace. Tracing can be very precise with Debug class method. Both tracing and TraceView are integrated in Android Studio DDMS tool. Simpleper