<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gradle-Profiler on Telltale — Gradle build experiment results</title><link>https://cdsap.github.io/Telltale/caches/gradle-profiler/</link><description>Recent content in Gradle-Profiler on Telltale — Gradle build experiment results</description><generator>Hugo -- 0.145.0</generator><language>en-us</language><lastBuildDate>Sun, 18 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://cdsap.github.io/Telltale/caches/gradle-profiler/index.xml" rel="self" type="application/rss+xml"/><item><title>[Catchup] anvil vs metro - incremental build</title><link>https://cdsap.github.io/Telltale/posts/2025-05-18-profiler-cdsap-18-experiment/</link><pubDate>Sun, 18 May 2025 00:00:00 +0000</pubDate><guid>https://cdsap.github.io/Telltale/posts/2025-05-18-profiler-cdsap-18-experiment/</guid><description>The analysis of the Gradle build performance data reveals a notable improvement in overall build times when comparing variant B (metro_0_3_2) to variant A (anvil). Specifically, variant B is faster by approximately 6.7 seconds (26.012s for A vs. 19.291s for B), translating to a 25.8% decrease in build time. This improvement is consistent across the 50th and 90th percentiles as well. In task execution, the &lt;code>:app-scaffold:compileDebugKotlin&lt;/code> task shows a significant increase in execution time in variant B, while &lt;code>:app-scaffold:kspDebugKotlin&lt;/code> is notably faster. The Kotlin build reports highlight a substantial increase in IR translation time for variant B, suggesting a potential area for optimization. Memory and CPU usage are slightly higher in variant B for all processes, with the build child processes in variant B utilizing significantly more CPU resources. Lastly, garbage collection data indicates fewer total collections in variant B, suggesting more efficient memory management.</description></item><item><title>CatchUp using Metro with abi scenario</title><link>https://cdsap.github.io/Telltale/posts/2025-04-10-profiler-cdsap-17-experiment/</link><pubDate>Thu, 10 Apr 2025 00:00:00 +0000</pubDate><guid>https://cdsap.github.io/Telltale/posts/2025-04-10-profiler-cdsap-17-experiment/</guid><description>The performance comparison between &lt;code>varianta_main&lt;/code> and &lt;code>variantb_z/metro&lt;/code> reveals that &lt;code>variantb_z/metro&lt;/code> generally has a shorter build time with a mean reduction of 25.1% (6.622 seconds). Notably, &lt;code>variantb_z/metro&lt;/code> also exhibits higher CPU usage in build child processes, suggesting more intensive parallel task execution. In the Kotlin Build Reports, &lt;code>variantb_z/metro&lt;/code> shows a significant increase in Compiler IR translation time, which could indicate more complex translation processes. Memory usage is slightly lower in &lt;code>variantb_z/metro&lt;/code> across all processes, contributing to its efficiency.</description></item></channel></rss>