From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

thanks for the advice, this is the result for async profiler from :appentry:mergeGeneralDebugResources. But how exactly to trigger only configuration time from command line (for full build on android project)?  so the trace below contains ~38 sec for init, and 24.265s from executing task.  From the trace seems g1gc spent pretty large amount of time.

sorry for the late reply, it is the result after disable configure and demand, enable --async-profiler-system-threads=true, but i need to use frame interval to 2x of default because buffer overflow error. It seems half of it spend for javaThread, is that something related to GC ? Actually this profile only for 25-30 sec of configuration, because i am not run full build and only run small task that trigger full configuration. When running full build seems it increased a little bit compared to this.

It was 1 warmup,I also forgot to say it is cold daemon, and i run clean build. Below are the result from 4 warm ups, seems not much differences between them.  what are things that may causing classloaders recreated ? is it probably because plugin, libraries or our configuration  ?