Status Update
Comments
ff...@gmail.com <ff...@gmail.com> #3
Actually these transforms are only ~40% of the time spend in there, but it's still a hot spot that we should resolve by not using a FileCollection
ff...@gmail.com <ff...@gmail.com> #4
xav@ could you assign this bug to someone to make sure it gets fixed?
ff...@gmail.com <ff...@gmail.com> #5
Jerome will do that for you :)
ri...@google.com <ri...@google.com>
je...@google.com <je...@google.com>
so...@google.com <so...@google.com> #6
Bingran, can you have a look at this asap. thx !
ff...@gmail.com <ff...@gmail.com> #7
To make sure I analyze the "buildOnServer-7.5-rc-2-2022-07-01-shutdown.snapshot" correctly, I attached a screenshot of how I find the concerning point. From the picture, the MergeGeneratedProguardFilesCreationAction takes 1924ms. Is that the right way to check your snapshot file? If so, what is the expected time for that creation action in a config cached build?
so...@google.com <so...@google.com> #8
I think you missed adding an attachment.
so...@google.com <so...@google.com> #9
oops, here it is =)
so...@google.com <so...@google.com> #10
From discussions with xav@ that time should almost be non-existent during the run when the configuration cache kicks in.
sm...@google.com <sm...@google.com> #11
I checked out androidx-main, is that the right one? There is no gradlew file under that directory.
bingran@bingran-linux-west:~/androidx-main/tools$ ls
external fetch_artifact metalava repohooks
And have you ever tried building androidx with the dev version of AGP(the one built from studio-main)?
ff...@gmail.com <ff...@gmail.com> #12
I checked out androidx-main, is that the right one? There is no gradlew file under that directory.
Yes, aosp androidx-main is the repo. You'll want to use frameworks/support/gradlew
thats the main repo all the work is done.
And have you ever tried building androidx with the dev version of AGP(the one built from studio-main)?
Yes we have a script for that
namely you can set a number of variables to use the latest AGP (
- GRADLE_PLUGIN_VERSION
- LINT_VERSION
- GRADLE_PLUGIN_REPO
and then run frameworks/support/gradlew
qu...@gmail.com <qu...@gmail.com> #13
I believe this issue can be fixed by Jerome'CL ag/19955912. I got 4 snapshots running androidx to verify the fix.
- the first run without the fix
- the second run(config cached) without the fix
- the first run with the fix
- the second run(config cached) with the fix
From the snapshot of secondWithFix_xxx
, if we do a search for MergeGeneratedProguardFilesCreationAction
in the call tree, nothing would show up. However, if we do the same search for secondWithoutFix_xx
, 3612ms is spent inside MergeGeneratedProguardFilesCreationAction
.
The fix also reduce the time spent in non config cached run if we compare the same thing for firstWithoutFix_xxx
and firstWithFix_xxx
ff...@gmail.com <ff...@gmail.com> #14
Great bug Aurimas, very useful to get such bugs filed.
Description
AI-213.7172.25.2113.9014738, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Windows 11(amd64) v10.0 , screens 1920.0x1080.0
AS: Dolphin | 2021.3.1
Kotlin plugin: 213-1.7.10-release-for-android-studio-AS6777.52
Android Gradle Plugin: (plugin information not found)
Gradle: 7.3.3
Gradle JDK: Oracle OpenJDK version 11.0.15
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read
SDK 31 ~ 33