[
https://issues.apache.org/jira/browse/BEAM-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156467#comment-17156467
]
Beam JIRA Bot commented on BEAM-10256:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Experiment with Jenkins Worker VM Sizes and # executors
> -------------------------------------------------------
>
> Key: BEAM-10256
> URL: https://issues.apache.org/jira/browse/BEAM-10256
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Tyson Hamilton
> Assignee: Tyson Hamilton
> Priority: P2
> Labels: Jenkins, infra, infrastructure, jenkins, stale-assigned
>
> When on the new Apache infra for Jenkins we should revisit the size of our
> VMs. Currently we use n1-highmem-16 but this may be wasteful since only 2
> executors are running on each worker.
>
> One option is to increase the number of executors on each worker, say to 8,
> so each executor has 2 vcpus. The upper limit is our desired thread
> parallelism per executor (i.e. tests) and the memory required for each.
> Another option is to downsize the VM to a n1-highmem-4 and keep 2 executors.
> There are probably others, we should do some analysis to see what makes sense.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
