commit | ad51e4de39b0826f6fb81ca2aad6da59cbbf67d1 | [log] [tgz] |
---|---|---|
author | Andrey Kulikov <andreykulikov@google.com> | Wed Jan 24 15:32:30 2024 +0000 |
committer | Andrey Kulikov <andreykulikov@google.com> | Tue Apr 23 11:47:24 2024 +0100 |
tree | fffebaaac33feab2cdc0afa2e6fe89783446933e | |
parent | 6ea27ebbc20f185e40102e26fdccf8101f4b30a2 [diff] |
Force prefetch if item is needed in the next frame for lazy layouts The current implementation has a logic where it allows performing a task if the prefetch runnable was executed when we already missed the frame. It is not the best strategy, instead we will be predicting when the next item will be needed in the next frame and only do forced prefetch ignoring the frame budget in this scenario. Note: the prefetch logic in staggered grids is nontrivial and this new behavior is not ported to staggered grids as part of this change. We will reconsider it in future. Results of running ComplexNestedListsScrollBenchmark: Before gfxFrameJankPercent min 23.0, median 33.8, max 45.5 frameDurationCpuMs P50 19.7, P90 31.1, P95 32.2, P99 36.5 frameOverrunMs P50 8.5, P90 24.6, P95 25.7, P99 30.8 After gfxFrameJankPercent min 8.5, median 12.8, max 24.7 frameDurationCpuMs P50 19.3, P90 25.6, P95 31.2, P99 36.0 frameOverrunMs P50 7.9, P90 22.8, P95 24.7, P99 31.5 Test: Run benchmarks, explored the traces and did a local testing via logs Relnote: LazyLayout prefetch requests can be marked as urgent now, meaning that we expect this item to be needed in the next frame and want to ignore frame budget to make sure to do more work in advance Change-Id: Id513f17517aa1b240e91afb3468837b12ed54da8
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.