You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Scott Wegner (JIRA)" <ji...@apache.org> on 2018/04/18 21:04:00 UTC
[jira] [Updated] (BEAM-4122) Tune Gradle resource usage on Jenkins
[ https://issues.apache.org/jira/browse/BEAM-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wegner updated BEAM-4122:
-------------------------------
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|https://scans.gradle.com/s/ehue5xqj36zeo/infrastructure] 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
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|https://docs.gradle.org/current/userguide/build_cache.html]: re-use up-to-date outputs from previous builds
* [Gradle Daemon|https://docs.gradle.org/current/userguide/gradle_daemon.html]: re-use worker process and cache output status
was:
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.
> Tune Gradle resource usage on Jenkins
> -------------------------------------
>
> Key: BEAM-4122
> URL: https://issues.apache.org/jira/browse/BEAM-4122
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Scott Wegner
> Assignee: Scott Wegner
> Priority: Major
>
> 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|https://scans.gradle.com/s/ehue5xqj36zeo/infrastructure] 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
> 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|https://docs.gradle.org/current/userguide/build_cache.html]: re-use up-to-date outputs from previous builds
> * [Gradle Daemon|https://docs.gradle.org/current/userguide/gradle_daemon.html]: re-use worker process and cache output status
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)