Interesting, I’ve started to feel similar pains though I’m only at 152 sub
projects so far.
I can’t offer any solutions yet as for the most part I’ve been able to manage.
On 09 Apr 2014, at 17:07, Xavier Ducrohet <x...@google.com> wrote:
> Hi,
>
> We have a large (for us?) projects with 122 sub-projects. With a warmed up
> daemon it takes about 49 seconds to run "gradlew projects".
>
> Trying to figure out what's taking time we ran it with --profile and the
> results were strange:
>
> - 1.6 seconds of startup/settings/buildSrc/loading up projects.
> - 8.4 seconds of project configurations
> - 6.9 seconds of dependency resolution
> - 0.1 seconds of task execution.
>
> This adds up to 17 seconds out of 49 seconds.
>
> My original intent was to see if I could improve configuration time by
> reducing the amount of work done during configuration and moving it to the
> execution phase, but it seems 2/3 of the time is spend somewhere else.
>
> Does it look like a typical profiling output? anything we can do to speed
> things up? (I tried with --parallel and got the same results)
>
> thanks
> Xav
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
