[BEAM-4122] Tune Gradle resource usage on Jenkins

• Type: Sub-task
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: Not applicable
• Component/s: build-system
• Assignee: Scott Wegner
• Reporter: Scott Wegner
• Created: 18/Apr/18 20:19
• Updated: 16/May/20 13:47
• Resolved: 24/Apr/18 22:22

Description

The new Gradle build seems to be exhausting memory on the Jenkins machines, causing them to lose their connection and die. This has made our tests extremely flaky.

We need to tune the Gradle build such that it does not exhaust Jenkins machine resources.

A  Gradle build scan shows some information about the Jenkins VM:

• Operating system Linux 3.19.0-79-generic
• CPU cores 4 cores
• Max Gradle workers 4 workers
• Java runtime Oracle Java(TM) SE Runtime Environment 1.8.0_152-b16
• Java VM Oracle Java HotSpot(TM) 64-Bit Server VM 25.152-b16 (mixed mode)
• Max JVM memory heap size 3506 MB

From the Jenkins Load Statistics page, it appears that each machine has 2 executors.

Some resources for tuning memory:

• https://wiki.jenkins.io/display/JENKINS/I%27m+getting+OutOfMemoryError 
• https://guides.gradle.org/performance/ 
• https://docs.gradle.org/current/userguide/build_environment.html#sec:configuring_jvm_memory 
• https://docs.gradle.org/current/userguide/command_line_interface.html#sec:command_line_performance 

 

We may also be able to improve performance by using Gradle features to remove redundant work:

• Build Cache: re-use up-to-date outputs from previous builds
• Gradle Daemon: re-use worker process and cache output status

Issue Links

• blocks: BEAM-3407 Frequent Jenkins failures due to "Backing channel 'beamN' is disconnected"
• links to: GitHub Pull Request #5171
• links to: GitHub Pull Request #5198