Status Update
Comments
co...@google.com <co...@google.com> #2
-
Is controlled by your ui automator commands - make sure to
so your gestures/flings/drags don't accidentally interact with system ui.set a gesture margin -
Please provide traces from runs that have issues, and we can look into them. Could be related to
b/279088460 -
We've had requests for this, and we'll consider it in 1.3, but two things make this hard:
3.1. Androidx has a no-protos-in-apis policy, so we'd have to pass you a binary config, and let you modify it (or at least pass in binary datasource protos or similar)
3.2 Perfetto configs aren't trivial to merge together
Do you have specific things you'd like to be in the perfetto config?
- There's an experimental (no guarantee of support) project in the androidx repo that parses and graphs benchmark output distributions, but it's more about diffing small sets of benchmark runs. That may be worth investigating:
https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:development/plot-benchmarks/
co...@google.com <co...@google.com>
ap...@google.com <ap...@google.com> #3
- about lag in perfetto Sorry , I forget to tell the background I use Macrobenchmark for.
I am in device maker company, I'm using this macrobenchmark framework to test system performance.
When the system get slow, perfetto will not start as meant to be, there'll a lag between the time when marobenchmark starts perfetto and the time when perfetto trace really starts recording.
-
trace file please see the screenshot and trace file I upload
-
data sources I'd like to add in perfetto config
because some jank frame doesn't matter, I only interested user percepted jank frame.
device maker add some trace to record user percepted jank fame in the trace
I need open it , so that I can read in the trace by sql querying.
- thanks , I will look it.
co...@google.com <co...@google.com> #4
is there any more detail explaination about
what does P button mean?
what does x axis mean for sampled metric and single value metric?
how does it normalize metrics? it seems y values are not between 0 and 1 after enable normalized metrics.
ap...@google.com <ap...@google.com> #6
Branch: androidx-main
commit ec13e616312e4026429dfa6a86b820725f30e2be
Author: Chris Craik <ccraik@google.com>
Date: Wed Dec 06 09:59:35 2023
Fix FrameId parsing in FrameTimingMetric
Fixes: 303823815
Bug: 306235276
Test: SliceTest
Test: FrameTimingQueryTest
Relnote: "Fixed crash in FrameTimingMetric failing to parse frame id,
especially on certain OEM devices."
Change-Id: Ia24bc3c90b317252f579cc2425547f034ef96ef8
A benchmark/benchmark-macro/src/androidTest/java/androidx/benchmark/perfetto/SliceTest.kt
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/macro/perfetto/FrameTimingQuery.kt
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/perfetto/Slice.kt
pr...@google.com <pr...@google.com> #7
thank you
Description
The following Experimental APIs have existed for several releases.
Please consider stabilising or removing these APIs: