Status Update
No update yet.
Comments
ml...@google.com
This information is added starting Android U (API 34)
cc...@google.com
I can put up a CL with this change, but I'm unclear when these show up, I'm not seeing much useful tracing in binder transactions in a random API 34 build
With AIDL:
Without AIDL:
And it looks like the tag and a lot of its functionality was google/sdk_gphone64_x86_64/emu64xa:14/UE1A.230829.036.A1/11228894:user/release-keys
ap...@google.com
Branch: androidx-main
commit 55533f46529e4f8772babe2852602138d51286e4
Author: Chris Craik <ccraik@google.com>
Date: Tue May 21 13:19:39 2024
Enable AIDL tracing by default in benchmark
Fixes: 341852305
Test: adb shell atrace --list_categories | grep aidl
Relnote: "Enable AIDL tracing by default (requires API 28)"
AIDL is on by default in many platform performance testing perfetto
configurations.
Change-Id: Ia0af2a55ac2635db68427845860dc96d93994220
M benchmark/benchmark-common/src/main/java/androidx/benchmark/perfetto/AtraceTag.kt
M benchmark/benchmark-common/src/main/java/androidx/benchmark/perfetto/PerfettoConfig.kt
ca...@google.com
From your CL comment it sounds like you figured this out in terms of finding the data. But yes, zimuzo@ added the "what is the actual aidl transaction" piece in U, which wasn't there before.
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.benchmark:benchmark-common:1.3.0-beta01
Description
Component used: Macrobench 1.3.0-alpha05
By default
binder transactioncalls are very enigmatic not providing info on what's going on. This can be improved by enablingAIDLatrace tag that would give some information in thebinder replyWhat do you think we add this tag as default in the macrobenchmark perfetto config?
Reference trace file: