commit | d101f5707ac2d364fdb8555d483e9ee24ab902ad | [log] [tgz] |
---|---|---|
author | Chris Craik <ccraik@google.com> | Tue Oct 10 16:38:12 2023 -0700 |
committer | Chris Craik <ccraik@google.com> | Wed Nov 15 10:56:03 2023 -0800 |
tree | d8a5f776c2a6088e2fc3bc79803fb6c7ac4d2833 | |
parent | 7cf8a1e5ec2ca8ac8230d77cab45a72e5fa2f6a7 [diff] |
Add BenchmarkRule.measureRepeatedOnMainThread Bug: 300472956 Test: ./gradlew bench:b-c:cC bench:b-j:cC Test: MainThreadBenchmark # validated via trace Relnote: "Added BenchmarkRule.measureRepeatedOnMainThread so main thread benchmarks (e.g. ones touching Views or Compose UIs) can avoid triggering ANRs, especially during large suites in CI." Note that this implementation is still not complete: * We don't (yet) throw if you run measureRepeated() on the main thread (e.g. @UiThreadTest) * Benchmark doesn't yield when sleeping due to thermal throttle * Benchmark starts measurement immediately upon resuming main thread work, without any re-warmup. In practice, tracking min values and resuming almost immediately means this has minimal impact * hard deadline is fairly relaxed currently, while we explore long running loops Note that this also changes iterationsRemaining from publishedApi -> RestrictTo(LIBRARY_GROUP), since it's only ever been used within BenchmarkRule.measureRepeated, which is locked to same library version as BenchmarkState. RestrictTo(LIBRARY_GROUP) is a more appropriate tag since tracking isn't necessary due to the same version constraint, and lets the junit4 module use the value directly, as it is now in measureRepeatedMainThread Change-Id: I5c86dd05d6eca4984805d13a18d22b39a2382b02
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.