On 10 Apr 2014, at 5:43 am, Xavier Ducrohet <x...@google.com> wrote:
> We can use --configuration-on-demand and it works fine when building (the > difference is pretty amazing actually). > > However when loading the project in the IDE (Android Studio in this case), we > need to build the model for all the projects and that takes time. There might be some things we can do to speed things up there. For example, if your model builders don’t need the tasks, we can skip creating and configuring the tasks - things like that. > > > On Wed, Apr 9, 2014 at 10:19 AM, casey.mcgi...@gmail.com > <casey.mcgi...@gmail.com> wrote: > I'm up to 86 sub-projects. Do you use --configuration-on-demand? If not this > should help with the startup time. Of course that and using the gradle > daemon. Lately I have not had any issues with either feature. > > I had one project that behaved incorrectly with configuration on demand, but > I was able to resolve it by adding explicit dependsOn directives to link some > tasks. > > - Casey > > > On Wed, Apr 9, 2014 at 5:43 AM, Sebastian Gozin [via Gradle] <[hidden email]> > wrote: > 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 <[hidden email]> 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 > > > > > If you reply to this email, your message will be added to the discussion > below: > http://gradle.1045684.n5.nabble.com/Overhead-when-configuring-many-projects-tp5712563p5712565.html > To start a new topic under gradle-dev, email [hidden email] > To unsubscribe from gradle-dev, click here. > NAML > > > View this message in context: Re: Overhead when configuring many projects? > Sent from the gradle-dev mailing list archive at Nabble.com. > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com