Aurimas Liutikas
banner
liutikas.net
Aurimas Liutikas
@liutikas.net
Software engineer working on AndroidX at Google. Gradle Fellow. He/him

www.liutikas.net/blog-posts/
https://www.liutikas.net/talks/
It sounds like a feature request to Gradle :)
November 10, 2025 at 8:09 PM
You can find it under performance/build Configuration. Take that time and divide it by number of projects under projects tap
November 10, 2025 at 8:05 PM
Do you use org.gradle.configuration-cache.parallel=true ?
November 9, 2025 at 7:58 PM
Reposted by Aurimas Liutikas
yup it's fully KMP/jpcompose and works great on Android and iOS!! But we're always interested in connecting with more KMP people to get help and tips.
November 6, 2025 at 12:39 AM
I still think it is valuable to split pre-execution vs execution times. If you really want to avoid measuring CC cost you can disable configuration cache and run with --dry-run
November 5, 2025 at 7:27 PM
You definitely want to pick a task that represents the workflow you want to optimize. If you never run licensee, skip it from your benchmarking.
November 5, 2025 at 7:12 PM
I think the correct term is "configuration cache serialization/store time" which happens after actual configuration is complete.
November 5, 2025 at 7:11 PM
It is definitely a balance. Picking the right task to benchmark is important. If you only ever run `assembleDebug` then that's what you want to benchmark. I just picked `build` since most folks are familiar with it and it gives a good starting point.
November 5, 2025 at 7:10 PM
Configuration time is technically not the correct term. It would be pre task execution time, but generally configuration time takes the bulk of that time because initialization is super fast and configuration serialization and deserialization can be thought as part of configuration time.
November 5, 2025 at 6:55 PM
I would love for you to write up your journey here into a blog post!
November 4, 2025 at 3:27 PM
Dependency Caching
docs.gradle.org
November 3, 2025 at 11:26 PM
Gradle does 0 caching for anything that has SNAPSHOT in the name. It will redownload with every invocation of Gradle. Highly recommend you move away from those versions.
November 3, 2025 at 11:25 PM
By the way, this is a second run after deleting CC entries or a clean build?
November 3, 2025 at 11:09 PM
Build scans generally happen on a background thread, so you need to see which parts run on the main Gradle daemon thread.
November 3, 2025 at 11:09 PM
Why are your transforms running all the time? Are you by any chance using -SNAPSHOT versions somewhere in your build classpath?

This looks suspect.
November 3, 2025 at 11:06 PM
😭
November 3, 2025 at 9:38 PM
I'll also happily accept a coffee from you if I ever meet you in person! :)
November 2, 2025 at 11:17 PM
I am very happy to hear these posts are valuable/

I want you to keep asking questions! Even better if you write a post answering someone else's questions. Sharing knowledge is the best way to improve our ecosystem!
November 2, 2025 at 11:13 PM