summaryrefslogtreecommitdiff
path: root/opengl/libagl/TextureObjectManager.cpp
diff options
context:
space:
mode:
author Alec Mouri <alecmouri@google.com> 2020-02-06 09:26:19 -0800
committer Alec Mouri <alecmouri@google.com> 2020-02-25 21:02:57 +0000
commit989ddbe046400612f92a05a71d38f438e4dd19e1 (patch)
tree894e1b961260486d5dfffcae318f41bc34dcd122 /opengl/libagl/TextureObjectManager.cpp
parent219643eebd19e550100f317ea52854bde4047d8f (diff)
[SurfaceFlinger] Push atoms on janky events
For now define a jank event as a window of 100ms containing at least one missed frame. On the server-side we can then configure whether tracing is triggered based on the number of missed frames in a window. A 100ms window should be safe, as always-on tracing should contain ~10 seconds of trace data Further details on when we report a jank: * We don't report a jank if it occurred more than a second in the past, since we need a good guarantee that the trace will actually contain the jank * We don't report a jank if the display is off or in doze, as missed frames in those power modes are either not actionable or not user-perceived. * We only report a jank on userdebug or eng builds. This will never be enabled on user builds, so there's no reason to incur the cost of pushing the atom on those builds. Bug: 148543048 Test: builds Test: statsd_testdrive 257 Change-Id: Ifc544d544ef8da9adec944507fe71dc5550c13e8 (cherry picked from commit 5f487d4e17ff7347e927f5e5b0a2a97c84ad16c7) Merged-In: Ifc544d544ef8da9adec944507fe71dc5550c13e8
Diffstat (limited to 'opengl/libagl/TextureObjectManager.cpp')
0 files changed, 0 insertions, 0 deletions