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 20:22:00 UTC

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

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

Scott Wegner commented on BEAM-4122:
------------------------------------

I've asked in INFRA-16380 about machine specs and performance characteristics of the build. Once I hear back I'll work on tuning Gradle's parameters.

Probably the main option to tune is the number of Gradle workers. I believe Gradle allocates workers according to number of CPU cores, and each one has 1GB or memory space.

> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)