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

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/02 17:07:02 UTC

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

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

Beam JIRA Bot commented on BEAM-10281:
--------------------------------------

This issue was marked "stale-assigned" and has not received a public comment in 7 days. It is now automatically unassigned. If you are still working on it, you can assign it to yourself again. Please also give an update about the status of the work.

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