https://kotlinlang.org logo
Channels
Powered by
#android
  • j

    jw

    01/11/2016, 7:02 AM
    Gradle contributes little to build times
  • j

    jw

    01/11/2016, 7:02 AM
    Switching to another tool that runs the same steps won't affect the times in any meaningful way
  • j

    jw

    01/11/2016, 7:05 AM
    Run with --dry-run and see its overhead
  • m

    mpcjanssen

    01/11/2016, 11:20 AM
    @apptreematt are you still using gradle 2.2? Switching to 2.4 will make a huge difference. 2.2 will eat all your memory. 2.4 is much better. I switched my android app yesterday and now i can run regular unit tests again without going insane.
  • m

    madisp

    01/11/2016, 11:24 AM
    2.10 has already shipped, why stop at 2.4? simple smile
  • m

    mpcjanssen

    01/11/2016, 11:25 AM
    ISTR 2.10 breaks the android plugin, but I could retry
  • m

    madisp

    01/11/2016, 11:28 AM
    yeah, if you're on 1.3.1 or older then it won't support 2.10
  • g

    Gabriel Ittner

    01/11/2016, 11:28 AM
  • m

    madisp

    01/11/2016, 11:28 AM
    because it'll erroneously think you're on 2.1 (yaaay for string compare)
  • m

    madisp

    01/11/2016, 11:30 AM
    bumping the android plugin to "1.5.0" fixes it though
  • m

    mpcjanssen

    01/11/2016, 11:32 AM
    hmm seems indeed that the combination 2.10 1.5.0 works (at least when using the proper way to update the wrapper)
  • m

    mpcjanssen

    01/11/2016, 11:37 AM
    great even faster, doing unit tests for a single flavor changed from 2 in2.2 minutes to 2 seconds in 2.10
  • m

    madisp

    01/11/2016, 11:38 AM
    2min -> 2sec?
  • m

    mpcjanssen

    01/11/2016, 11:41 AM
    yes, in 2.2 the gradle daemon quickly went to 1GB memory usage making unit tests slow like molasses. In 2.10 it takes 2 seconds.
  • m

    mpcjanssen

    01/11/2016, 11:42 AM
    everything is much faster in 2.2 configuring the projects already took 10 seconds on my machine
  • m

    mpcjanssen

    01/11/2016, 11:44 AM
    An initial test run on 2.2 would take around 30s but that time went up drastically after running it a couple of times. Eventually leading to an OOM
  • m

    mpcjanssen

    01/11/2016, 11:45 AM
    Anyway not a very scientific benchmark. Much faster seems about right simple smile
  • a

    apptreematt

    01/11/2016, 1:28 PM
    @mpcjanssen: I’m using gradle 2.10. Fresh build takes 1 min 20 sec. Making a simple change and rebuilding takes 26-30 sec.
  • m

    mpcjanssen

    01/11/2016, 1:31 PM
    And you are using the gradle daemon and parallel building?
  • a

    apptreematt

    01/11/2016, 1:32 PM
    Yes
  • a

    apptreematt

    01/11/2016, 1:32 PM
    -.csv
    -.csv
  • a

    apptreematt

    01/11/2016, 1:32 PM
    That didn’t format as well as I had hoped
  • a

    apptreematt

    01/11/2016, 1:33 PM
    That is for an incremental build.
  • m

    mpcjanssen

    01/11/2016, 1:34 PM
    you mean dexOptions = incremental ?
  • m

    mpcjanssen

    01/11/2016, 1:34 PM
    It would be interesting to see how long a --dry-run takes
  • a

    apptreematt

    01/11/2016, 1:35 PM
    1.59 seconds
  • a

    apptreematt

    01/11/2016, 1:35 PM
    I did ./gradlew assembleAppTreeDebug —dry-run
  • a

    apptreematt

    01/11/2016, 1:36 PM
    Not dex-options = incremental. I just mean after making a single line code change and re-building
  • m

    mpcjanssen

    01/11/2016, 1:36 PM
    yes but dex-options incremental (in build.gradle) makes that much faster
  • m

    mpcjanssen

    01/11/2016, 1:37 PM
    it wont have to redex the whole app. (IIUC)
1...673674675...1383Latest