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] < ml-node+s1045684n5712565...@n5.nabble.com> 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]<http://user/SendEmail.jtp?type=node&node=5712565&i=0>> > 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 > ml-node+s1045684n1436218...@n5.nabble.com > To unsubscribe from gradle-dev, click > here<http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1436218&code=Y2FzZXkubWNnaW50eUBnbWFpbC5jb218MTQzNjIxOHwxOTQ0Njk0NjE=> > . > NAML<http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://gradle.1045684.n5.nabble.com/Overhead-when-configuring-many-projects-tp5712563p5712566.html Sent from the gradle-dev mailing list archive at Nabble.com.
