Stuck in computeActualUsageDebug for many minutes about dependency-analysis-gradle-plugin HOT 6 OPEN

👋 @autonomousapps !

I too I am currently experiencing similar issues when running the buildHealth task. I am working on this woocommerce-android open source project and trying to set-up the plugin. It seems to be taking too long, the computeActualUsage* per se. Previously, about a year ago, when I tried running the plugin again, everything worked as expected (much faster).

You will find these changes within the build/dependency-analysis-android-gradle-plugin branch, just in case you would like to clone/pull the repo/branch and experienced it for yourself.

Build scan link (GRADLE_PROFILER)
https://gradle.com/s/j73i5752pltng

Plugin version
1.32.0

Gradle version
8.2.1

JDK version
openjdk 17.0.11 2024-04-16

(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
1.9.22

(Optional) Android Gradle Plugin (AGP) version
8.1.0

You could use gradle-profiler to profile the build for CPU and memory usage and see what seems to be taking so long.

I am also providing you with a profile.log report, which I generated running the below gradle-profile command, you'll find the build scans links within:

gradle-profiler --profile buildscan --project-dir ../woocommerce-android buildHealth

profile.log

I hope all this info will somewhat help you with your investigation, and thank you! 🙏

from dependency-analysis-gradle-plugin.

Thanks for the issue. My first thought was memory, and it still might be the case. Do you have a build scan you can share?

You could use gradle-profiler to profile the build for CPU and memory usage and see what seems to be taking so long. I would run just the task in question to keep the profile useful. I'm happy to take a look if you're willing to share the reports. I have done so in the past.

from dependency-analysis-gradle-plugin.

hey @autonomousapps , I sent you some data by email a few days ago using your email listed on your profile. Did you check that? I will try to find time for a better analyses if it is not enough.

from dependency-analysis-gradle-plugin.

hey @autonomousapps , I sent you some data by email a few days ago using your email listed on your profile. Did you check that? I will try to find time for a better analyses if it is not enough.

I did see the email, thanks!

from dependency-analysis-gradle-plugin.

👋 @autonomousapps !

To follow-up on this, today I was trying older versions on the plugin and the problem persisted till version 1.30.0.

Now, that doesn't mean that version 1.29.0 worked, actually this version produced a could not determine the dependencies of task kind of failure (see dependency-analysis-failure-v1.29.0.txt).

But then, version 1.28.0 worked as expected, with the buildHealth task no longer being stuck in computeActualUsage phase for minutes. 🤔

I hope the above will help you somehow and many thanks for all the work with this plugin! 🥇

from dependency-analysis-gradle-plugin.

--profile buildscan isn't super userful for investigating this, unfortunately. I need to know what's happening in the CPU -- the build scan is too coarse grained. Can someone run gradle-profiler --profile async-profiler on their project?

from dependency-analysis-gradle-plugin.