has been developed using Android studio for more than a year, as the project grows, relying on the increase of the library, the construction speed is more and more slow, now the slowest 6 minutes to build a release of the installation package, find information on the Internet, found that can be configured to speed up the pace, Here to share with you.
Turn on gradle separate daemon
Create the file under the following directory gradle.properties
:
/home/<username>/.gradle/
(Linux)
/Users/<username>/.gradle/
(MAC)
C:\Users\<username>\.gradle
(Windows)
and add in the file:
Modifying the files under the project gradle.properties
can also be optimized:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21st 22 23 24 25 26 27 28
|
# project-wide Gradle settings.
# IDE (e.g. Android Studio) Users: # Settings specified in this file would override any Gradle Settings # configured through the IDE.
# For more details about how to configure your build environment visit # http://www.gradle.org/docs/current/userguide/build_environment.html
# The Gradle daemon aims to improve the startup and execution time of Gradle. # When set to True the Gradle daemon are to run the build. # todo:disable daemon on CI, since builds should is clean and reliable on servers Org.gradle.daemon=true
# Specifies the JVM arguments used for the daemon process. # The setting is particularly useful for tweaking memory settings. # Default Value:-xmx10248m-xx:maxpermsize=256m Org.gradle.jvmargs=-xmx2048m-xx:maxpermsize=512m-xx:+heapdumponoutofmemoryerror-dfile.encoding=utf-8
# when configured, Gradle'll run in incubating parallel mode. # This option is should only is used with decoupled projects. More details, visit # http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects Org.gradle.parallel=true
# enables new incubating mode that makes Gradle selective when configuring projects. # only relevant projects is configured which results in faster builds for large multi-projects. # Http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:configuration_on_demand Org.gradle.configureondemand=true
|
At the same time, these parameters can also be configured in the previous user directory in the gradle.properties file, so it is not for a project to take effect, but for all projects to take effect.
The above configuration file is mainly to do, increase the size of Gradle running Java Virtual machine, let gradle at compile time use independent process, let Gradle can run parallel.
Modify the Android Studio configuration
In the configuration of Android Studio, turn on offline mode and modify the configuration. The actual configuration is the same as in the above section, where the configuration is only effective when the IDE is built and the command-line build does not take effect.
Command line Build
Based on the above configuration, the command line is built with this parameter appended to the command --daemon --parallel --offline
.
Using AAR when importing dependent libraries
Use AAR as much as possible using the Web-based third-party dependency library, which can be searched in mavenhttp://gradleplease.appspot.com/or Githuhttps://github.com/goddchen/mvn-repo.
Own library module can also be packaged into AAR, about this can refer to Stormzhang article http://www.stormzhang.com/android/2015/03/01/android-reference-local-aar/.
Postscript
After such a toss, I originally need 4, 5 minutes to build the completed project, now only 30 seconds or so can be built to complete. Of course, if you do not do so, then, you should change the computer, SSD hard disk, larger memory, must be on the.
Other than that
Modify the Idea.xxx.vmoptions/studio.xxx.vmoptions file in the Bin folder in your idea/android Studio installation directory
&lt;img src= "https://pic1.zhimg.com/cf19ab821dbfa741acdab940e165bc30_b.jpg" data-rawwidth= "570" data-rawheight= "366" class= "Origin_image zh-lightbox-thumb" width= "570" data-original= "https://pic1.zhimg.com/ Cf19ab821dbfa741acdab940e165bc30_r.jpg "&gt;
My value
-xms512m
-xmx2048m
-xx:maxpermsize=768m
-xx:reservedcodecachesize=768m
-xx:+usecompressedoops
Android Stuido as Google's main push IDE, with Gradle compilation, there are many advantages and convenience. The only use of the process of uncomfortable place is inexplicably, often in the coding when the card, very silent, do not know is not my machine is also rotten, in short, IDE optimization also need Google refueling. And very slow compilation speed. Tried a lot of optimization programs, and I will share my findings with you.
Take PC-side for example, Mac is similar
1. Request Large Memory
Installation Path\studio64.exe.vmoptions or Studio.exe.vmoptions
Open with a text editor and find the starting two lines, as follows
-xms128m
-xmx750m
Modify minimum and maximum values, recommended for
-xms256m
-xmx2048m
2 Optimizing compilation
A:
File->setting->compile
Tick other options except for the second item and fill in the VM options:
-xmx2048m-xx:maxpermsize=512m-xx:+heapdumponoutofmemoryerror-dfile.encoding=utf-8
B:
C:\Users\yourname\.gradle
Open the gradle.properties with a text editor, and edit the following:
Org.gradle.daemon=true
Org.gradle.jvmargs=-xmx2048m-xx:maxpermsize=512m-xx:+heapdumponoutofmemoryerror-dfile.encoding=utf-8
Org.gradle.parallel=true
Org.gradle.configureondemand=true
After testing, the compilation speed has been greatly improved, compared to the larger items from the previous 5-8 minutes can be reduced to 1-2 minutes.
Accelerate Android Studio/gradle Build