[jira] [Work logged] (BEAM-4122) Tune Gradle resource usage on Jenkins

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-4122?focusedWorklogId=92243&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-92243 ]

ASF GitHub Bot logged work on BEAM-4122:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Apr/18 21:27
            Start Date: 18/Apr/18 21:27
    Worklog Time Spent: 10m 
      Work Description: swegner opened a new pull request #5171: [BEAM-4122] Tune Gradle resource usage on Jenkins
URL: https://github.com/apache/beam/pull/5171
 
 
   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.
   
   ------------------------
   
   Follow this checklist to help us incorporate your contribution quickly and easily:
   
    - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
    - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue.
    - [ ] Write a pull request description that is detailed enough to understand:
      - [ ] What the pull request does
      - [ ] Why it does it
      - [ ] How it does it
      - [ ] Why this approach
    - [ ] Each commit in the pull request should have a meaningful subject line and body.
    - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 92243)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
> From the [Jenkins Load Statistics|https://builds.apache.org/computer/beam3/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|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)