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/09/18 17:08:02 UTC
[jira] [Commented] (BEAM-10256) Experiment with Jenkins Worker VM
Sizes and # executors
[ https://issues.apache.org/jira/browse/BEAM-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198457#comment-17198457 ]
Beam JIRA Bot commented on BEAM-10256:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: Jenkins, infra, infrastructure, jenkins, stale-P2
>
> 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)