Ken Yee

Looks like Android Studio sync actually has 5 numbers which aren't documented well. 1st value is full Sync time (total of 4th and 5th values) 2nd value is gradle invocation...

> For Android Studio sync: Android Studio (IntelliJ) can run mutliple syncs in case you have `buildSrc`. So `Gradle invocation 1` is most likely project sync and `Gradle invocation 2`...

> For Android Studio sync: Android Studio (IntelliJ) can run mutliple syncs in case you have `buildSrc`. So `Gradle invocation 1` is most likely project sync and `Gradle invocation 2`...

What's additionally weird is that running gradle-profiler with: ``` gradle-profiler --cli --no-daemon ``` Causes gradle to run w/o a daemon at all...i.e., if you have a gradle plugin/task that tries...

https://github.com/gradle/gradle-profiler/blob/cd4881ceb74b7c2c14f60c58c18d2239157f172b/src/test/groovy/org/gradle/profiler/ProfilerIntegrationTest.groovy#L1303 Saw this in the unit test code... looks like you can set daemon=cold as well

I hit this as well using latest from master doing AS sync...looks like there used to be a way to turn this polling off: https://github.com/gradle/gradle-profiler/issues/63

also FWIW, when I did get clear-android-studio-cache-before = SCENARIO to run, it seemed a bit pessimistic. It recorded 10min sync times. I guess this includes building the model? When I...

Thanks for the explanation of what that setting does...would be worth adding to the docs :-) For our use case, we have the full app and smaller mini-apps for feature...

No worries...I did look through the gradle-profiler code a bit but couldn't figure out how it's communicating w/ AS (what technique...file, socket, etc). Logs aren't super helpful because the IDEA...

In comparison, running using the --no-build-cache parameter to the gradle command gives more consistent clean build results of roughly 15min: ``` tasks,:app:tfa:assembleDefaultDebug value,total execution time warm-up build #1,879473 measured build...