google / google/walt

About fastpath mode in screen latency test

Open
#121 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
473
Forks
74
PR merge metrics
No merged PRs in 30d

Description

There is fastpath mode in screen latency test, In the code it invoke "setSharedBufferMode" method which means use single Buffer to render and display. But from the systrace of fastpath test, the graphicBuffer was dequeued and queued normally, and there is 2 graphicBuffer:SurfaceView - org.chromium.latency.walt/org.chromium.latency.walt.MainActivity#0:0 and SurfaceView - org.chromium.latency.walt/org.chromium.latency.walt.MainActivity#0: 1。

So the queston is:
1. Does fastpath mode use the single Buffer mode?
2. If so, why the fastpath mode use 2 graphic Buffer, does it need hardware support?
Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.