Can I instrument my build script?

Old Forum
1

I’m having severe performance issues with my build script. The root project takes 100 seconds to configure, after the which the subproject take only a few milliseconds. I’m wondering where it’s spending it’s time: Is there any way to instrument my build script (a single build.gradle script) to see on what line it’s spending it’s execution time?

2

Hi Anne Try running gradle with the ‘–profile’ command line option. It’s not as granular to the line level, though it’s a start.

The --info and --debug flags will also provide more insight to which you may want to do some manual debug logging in suspected hot areas.

You can run a Java Profiling tool across your Gradle build also.

Although not specific to your case, this post may yield some additional suggestions to help with configuration times. http://stackoverflow.com/questions/21005180/why-does-my-large-multi-project-gradle-build-start-up-slowly

Any further questions please let us know

Kon

3

Hi Anne 
Try running gradle with the ‘–profile’ command line option. It’s not as granular to the line level, though it’s a start. 

The --info and --debug flags will also provide more insight to which you may want to do some manual debug logging in suspected hot areas. 

You can run a Java Profiling tool across your Gradle build also. 

Although not specific to your case, this post may yield some additional suggestions to help with configuration times. 
http://stackoverflow.com/questions/21… 

Any further questions please let us know 

Kon
(edit: posted under different account)

4

In addition to Kon’s suggestions, you might want to also try the Gradle Analytics Visualizer.