You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:02:02 UTC

[jira] [Updated] (BEAM-10281) Jenkins Load Sharing Improvements

     [ https://issues.apache.org/jira/browse/BEAM-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-10281:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Jenkins Load Sharing Improvements
> ---------------------------------
>
>                 Key: BEAM-10281
>                 URL: https://issues.apache.org/jira/browse/BEAM-10281
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Tyson Hamilton
>            Priority: P2
>
> Jenkins has 16 agents that run two executors on n1-highmem-16 (16 vCPUs, 104 GB memory) vms on GCE. The nodes appear to be far underutilized (CPU, MEM, IO):
>  
> With 12 jobs in the queue, a sampling of the agent VMs show:
> CPU hovers around 10-30% utilization
> Memory hovers around 2-15%
>  
> These configurations should be revisited to either increase the number of executors per agent or decrease the VM size and increase the number of VMs.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)