面包实验(Bread Test): jvmargs 对 Android studio 3.4.x的影响

Gradle版本

distributionUrl=https\://services.gradle.org/distributions/gradle-5.1.*-all.zip

目标文件名称

gradle.properties

目标文件内容

# Project-wide Gradle settings.
# IDE (e.g. Android Studio) users:
# Gradle settings configured through the IDE *will override*
# any settings specified in this file.
# For more details on how to configure your build environment visit
# http://www.gradle.org/docs/current/userguide/build_environment.html
# Specifies the JVM arguments used for the daemon process.
# The setting is particularly useful for tweaking memory settings.
org.gradle.jvmargs=-Xmx2816m
# When configured, Gradle will run in incubating parallel mode.
# This option should only be 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

android.useAndroidX=true
android.enableJetifier=true

IDE--Android Studio版本及运行环境，包括OS操作系统、JVM版本

Android Studio 3.4.x
Build #AI-***.*************, built on May 2, 2019
JRE: 1.8.0_*** ****** **** amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

这里试验的是目标文件中 “org.gradle.jvmargs=-Xmx2816m”对Android Studio的build编译效率的影响。也即是gradle对jvm虚拟机内存允许的最大内存限制对Android Studio编译效率的作用。多余的话不说，现在就开始实验吧。接下来，笔者会测试各个内存限制值下，对同一项目编译（Build）和清理（Clean）完成时长的对比。

假设 G==1GB==1024MB，

1. org.gradle.jvmargs=-Xmx[0.25G]

Clean