IssueTracker

Thanks for your detailed post.

However, benchmark build type is under configured: at least isProfileable is not set to true for existing build type, probably there's more.

We should set isProfileable = true by default when overriding an existing benchmark build type.

This issue is not about some specific configuration flag, but the general approach of dealing with external configuration. As a developer adopting baseline profiles, it seems extremely risky to me using a custom configuration due to how it's applied under the hood and the fact it may break default configuration.

I agree that is not great but this is a little tricky to do. For custom baseline profile build types we override all the properties. For benchmark I left it open to configure but it's mostly about these 2 properties:

isMinifyEnabled
isShrinkResources

I don't have a way to see if the user is setting them before overriding, so for this reason, I'd prefer not to. I agree with you that some other properties could be set by default to make this easier, i.e.:

isJniDebuggable = false
isDebuggable = false
isProfileable = true

The reason why I mentioned the release signing config in the beginning is because I want to use debug signing config.

In the specific of your issue, i.e. using a debug certificate can you override the benchmark and baseline profile setting? You should be able to do something like:

android {
    buildTypes {
        release { ... }
        debug { ... }
        benchmarkRelease {
            ...
            signingConfig signingConfigs.debug
        }
        nonMinifiedRelease {
            ...
            signingConfig signingConfigs.debug
        }
    }
}

Project: platform/frameworks/support
Branch: androidx-main
Author: Marcello Albano <maralb@google.com>
Link:      https://android-review.googlesource.com/3303459

Added override for debuggable and profileable for benchmark builds in bpgp

Added override for debuggable and profileable for benchmark builds in bpgp

Test: ./gradlew :benchmark:benchmark-baseline-profile-gradle-plugin:test
Bug: 369213505
Relnote: "isProfileable is always overridden in benchmark builds,
  and isDebuggable is also now always overridden in both benchmark and
  nonMinified (baseline profile capture) builds."
Change-Id: I487fa71083921682173f04fcbb477be5baf165f8

I've landed a change that will set the following properties also when the benchmark build type already exists:

isJniDebuggable = false
isDebuggable = false
isProfileable = true

As well as the following for agp 8.0:

isDebuggable = false

I'm going ahead and closing this - if you've further questions please answer here and will reopen. Thanks.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.benchmark:benchmark-baseline-profile-gradle-plugin:1.4.0-alpha04

Since release signing config is used by default instead of debug is not mentioned in release notes - maybe this is a bug?

Cause the last time I found it mentioned in the release notes was in version 1.1

signingConfig.debug is used as the default signing config (b/153583269)

So, if the switch to the release one indeed happened - maybe it's an issue?

The new build types should inherit the certificates from the release build type, unless none is specified in which case debug is used: code link

This should be updated in the documentation, thanks for mentioning it. Will take care of updating it.

So , I have to enlarge the trace buffer ( My device has 12GB memory), remove some trace event

Where can I get this project source code ? androidx.benchmark:benchmark-macro

Did the tracing buffer increase improve the problem?

Where can I get this project source code ? androidx.benchmark:benchmark-macro

Here: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:benchmark/benchmark-macro/

or mirrored on github: https://github.com/androidx/androidx/tree/androidx-main/benchmark/benchmark-macro

If you want to experiment with different perfetto capture configs you can also use this API: https://developer.android.com/reference/kotlin/androidx/benchmark/perfetto/PerfettoTrace#record(kotlin.String,kotlin.collections.List,kotlin.String,kotlin.Function1,kotlin.Function0) instead of macrobenchmark (which uses that API internally to collect traces from benchmarks).

thank you

I have a question about perfetto command.

as I found that, the data sources wasn't started after just run the perfetto command so I want to use --background-wait options, to let perfetto wait data sources started , then return.

I also worry about perfetto command process would killed by lmk, so I want to use detach mode to run perfetto, but --background-wait and detach mode are mutually exclusive.

how to achieve my goal: 1、return until all data sources start, 2、 run in background

If perfetto is started from an adb shell, it cannot be killed by LMKD. So you can safely use --background-wait without worrying.

--detach is realy reserved exclusively for the System Tracing app and should not be used by others.

thank you

It works after enlarge the buffer size and always use --background-wait option ( I have used wsl in windows , following the directions in https://github.com/androidx/androidx/blob/androidx-main/docs/onboarding.md, used benchmark:<project name>:assemble to generate my own aar files)

Thank you.

by the way, is there better way to simulate high system loads in android during benchmark test?