【性能】【beta】卡顿丢帧问题分析

性能问题会关注  cpu  io  内存；

1. 1、卡顿丢帧日志搜索关键字：

• binder  : Slow transaction consume   binder耗时以及堆栈打印
• binder_sample: [android.hardware.input.IInputManager,5,30002,com.android.commands.monkey,100] ：java层的binder调用超过X00ms打这个log

binder_sample:[binder的desc,transaction code,耗时,进程名,相对于阀值的百分比]

• Choreographer的跳帧信息：Choreographer: Skipped 36 frames! The application may be doing too much work on its main thread.

TAG, “Skipped ” + skippedFrames + ” frames! ” + “The application may be doing too much work on its main thread.”)  这里是收到vsync和处理这个vsync的时间太长超过大概30ms就会打印,说明应用主线程比较忙；

TAG是Choreographer Log.w(TAG, “Already have a pending vsync event. There should only be ” + “one at a time.”);   还有个vsync没有处理又新来了一个vsync； 

• SurfaceFlinger合成时跳帧：

SurfaceFlinger: Backpressure trigger, skipping transaction & refresh! 

• Looper消息处理时间过长：