Use only those dependencies that you need.To improve the performance we need to fix the version in place. This is how the gradle.properties file should look like:Ĭompile ':android-maps-utils:0.4+'.ĭynamic Dependencies slow down your build since they keep searching for the latest builds every time. It should only be used if you have available memory more than 2 GB. The above line is used to allow Java compilers to have available memory up to 2 GB (2048 MB). =-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 Using pre-built artifacts in the place of building dependent projectsĪdding the following line of code also aids us in speeding up the build.Re-using the configuration for unchanged projects.Besides that it also gives us other benefits such as The above line of code enables compilation of multiple modules at the same time. Adding this would consume some extra memory while building. Open up the gradle.properties file from the root of your project.If you need to modify or add a new dependency you’ll have to disable this option else the build would fail. Note: This only works if all the dependencies are downloaded and stored in the cache once. This will not allow the gradle to access the network during build and force it to resolve the dependencies from the cache itself. Enable gradle Offline Work from Preferences-> Build, Execution, Deployment-> Build Tools-> Gradle.This happens due to the fact that the module needs to be built from the scratch every time. A module takes 4x greater time than a jar or aar dependency. There are many cases where we need to fork the library to modify it to fit according to our needs.
#HOW TO SPEED UP PROJECT 64 EMULATOR UPDATE#
Generally with every new update there is a significant improvement in performance.
Make sure you’re using the latest version of Gradle.