Raise the Gradle daemon heap of the Android lint tasks in CI to 16 GB
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(firefox163 fixed)
| Tracking | Status | |
|---|---|---|
| firefox163 | --- | fixed |
People
(Reporter: ahochheiden, Assigned: ahochheiden)
References
(Blocks 2 open bugs)
Details
Attachments
(1 external file)
The Android lint tasks in CI run the Gradle daemon with the 7 GB heap from org.gradle.jvmargs in gradle.properties:
https://searchfox.org/firefox-main/rev/d9bd6be9a67efb1c2667ef91a89856f35eb7cf5e/gradle.properties#12
In the fenix lint that heap stays nearly full, with about 15 full garbage collections a run. With 16 GB, :fenix:lintAnalyzeDebug took 165s instead of 182s and the whole Gradle run 13s less on try (380s against 393s, medians of 4 runs).
These tasks run on b-linux-docker-large-amd workers with about 120 GB of memory:
https://searchfox.org/firefox-main/rev/d9bd6be9a67efb1c2667ef91a89856f35eb7cf5e/taskcluster/kinds/source-test/mozlint-android.yml#17
Developer machines vary, so the larger heap should apply only to these CI tasks and leave the other org.gradle.jvmargs unchanged.
| Assignee | ||
Comment 1•7 days ago
|
||
The 7 GB heap of the fenix lint stays nearly full, with about 15 full
GCs a run. With 16 GB, lintAnalyzeDebug took 165s instead of 182s
and the whole build 13s less (380s against 393s on try). The lint tasks
run on workers with about 120 GB, but developer machines vary, so the
heap is an env var, MOZ_GRADLE_MAX_HEAP, and gradle.properties
stays at 7 GB. The env var replaces only the -Xmx of
org.gradle.jvmargs, so the other arguments stay identical and a
running daemon is still reused.
Comment 3•14 hours ago
|
||
| bugherder | ||
Description
•