New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ComputeUsagesTask taking 30+ minutes to execute when it used to take 30 seconds for the same project #1136
Comments
Are you using the configuration cache? |
No, configuration cache was not enabled for either run. No, configuration cache was not enabled for either run. |
Can you try 1.30.0? If you get the same results, I'd like to see CPU and memory profiles to investigate. The biggest change between 28 and 29 is using the new AGP APIs. 30 makes further improvements in this vein. If you're not already doing it, I would suggest disabling auto-apply behavior and instead manually applying DAGP to each module. |
I saw the same results using 1.30.0 which is where I first noticed it. I dropped back to 1.29.0 first and then 1.28.0 before the regression went away. I am relying on the auto apply; I'll try running without it. I am upgrading to AGP 8.2.2 right now so I'll see if that makes any difference. If none of that proves to help, I'll get cpu and memory usage on it. |
I wonder if memory usage went up and you're GC thrashing. Could you take a look in the performance tab of your build scans and see what's happening with your memory? |
Build scan link
I have buildscans on company's internal instance if need info.
Plugin version
Seeing in 1.29.0 and 1.30.0
Gradle version
8.6
JDK version
17
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
1.9.20
(Optional) Android Gradle Plugin (AGP) version
8.1.4
Describe the bug
When running
projectHealth
,ComputeUsagesTask
increased from ~30s to ~40m after upgrading to version 1.29.0 on our mainapp
module.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Additional context
The text was updated successfully, but these errors were encountered: