Summary
The analysis of Gradle build performance between varianta_gradle_9_2_0 and variantb_gradle_9_1_0 reveals minor differences in build times, with varianta_gradle_9_2_0 showing a slight improvement. The mean build time for varianta is approximately 539.9 seconds compared to variantb at 542.4 seconds, a decrease of about 0.47%. Configuration times also show a marginal improvement in varianta with a mean time of 64.49 seconds versus 65.92 seconds for variantb, reflecting a 2.17% decrease. The most time-consuming tasks across both variants include :build-logic:convention:compileKotlin, :core:account:kspDebugKotlin, and :core:analytics:kspDebugKotlin, with varianta generally performing slightly better. Memory and CPU usage are nearly identical for both variants, with maximum values reaching up to 11.59 GB and 100% CPU usage respectively. Garbage collection activities are also comparable, with total collections close between the two variants.
Detailed Report
1. Build Time Comparison
Overall Build Time:
- Mean:
varianta: 539.9s,variantb: 542.4s (0.47% faster invarianta) - P50:
varianta: 537.0s,variantb: 541.8s - P90:
varianta: 560.1s,variantb: 566.9s
- Mean:
Configuration Time:
- Mean:
varianta: 64.49s,variantb: 65.92s (2.17% faster invarianta) - P50:
varianta: 63.81s,variantb: 65.60s - P90:
varianta: 69.06s,variantb: 70.41s
- Mean:
2. Task Type Differences
- Top Time-Consuming Tasks:
"org.jetbrains.kotlin.gradle.tasks.KotlinCompile": Mean times are identical at 1604ms for both variants."com.google.devtools.ksp.gradle.KspTaskJvm": Slightly longer invariantbwith a mean of 2727ms compared to 2719ms invarianta."com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask":variantais slightly faster with a mean of 2135ms compared to 2107ms invariantb.
3. Statistical Patterns
- Tasks such as
:build-logic:convention:compileKotlinand:core:account:kspDebugKotlinshow better performance invariantaacross mean, P50, and P90 metrics, suggesting more consistent build times invarianta.
4. Process State Analysis
Kotlin Process State:
- GC Time: Both variants show minimal differences, with
variantaat 0.49 andvariantbat 0.50.
- GC Time: Both variants show minimal differences, with
Gradle Process State:
- GC Time: Identical at 0.21 for both variants, with a slight increase at P90 for
variantb.
- GC Time: Identical at 0.21 for both variants, with a slight increase at P90 for
5. CPU & Memory Usage Analysis
All Processes:
- CPU Usage: Maxed at 100% for both variants.
- Memory Usage: Max of 11.59 GB for both, with slight variations in P50 and P90 values.
Build Process:
- CPU Usage: Slightly higher in
variantawith a max of 97% compared to 96% invariantb. - Memory Usage:
variantauses slightly more, peaking at 5.84 GB compared to 5.80 GB invariantb.
- CPU Usage: Slightly higher in
Build Child Processes:
- CPU Usage: Nearly identical, peaking at 96%.
- Memory Usage:
variantauses slightly less, with a max of 4.81 GB compared to 4.86 GB invariantb.
6. Garbage Collection Analysis
- Total GC Collections: Very close, with
variantaat 165 andvariantbat 168 collections.
This analysis highlights the minor improvements in build performance and efficiency in varianta_gradle_9_2_0 compared to variantb_gradle_9_1_0, particularly in configuration times and some key tasks, although both variants show similar resource usage and garbage collection metrics.