[
https://issues.apache.org/jira/browse/YARN-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202671#comment-16202671
]
Allen Wittenauer commented on YARN-7170:
----------------------------------------
Using HADOOP-14945 (which fixes docker -i mode when GPG signing isn't
required), I ran two builds on ASF Jenkins, each using this command line:
{code}
dev-support/bin/create-release --docker --native --dockercache
{code}
Once with plain trunk+14945 an once with the -02 patch. My understanding is
that bower and friends cache in the home directory. By running each build in
separate Docker containers with their own home dirs and their own maven repo
caches, nothing should get cached between the two builds.
As a result, the -02 patch cuts build time by ~3 minutes. Of course, the ASF
also has a significantly faster network pipe than if you were building at home.
Additionally the node I was running on wasn't doing much during the first run
but got another job scheduled during the second run. As a result, times here
should be viewed as conservative.
It'd be great if someone else can confirm that upgrading the frontend plugin
has a significant impact on the build time.
> Investigate bower dependencies for YARN UI v2
> ---------------------------------------------
>
> Key: YARN-7170
> URL: https://issues.apache.org/jira/browse/YARN-7170
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
> Reporter: Sunil G
> Assignee: Sunil G
> Priority: Critical
> Attachments: YARN-7170.001.patch, YARN-7170.002.patch
>
>
> [INFO] bower ember#2.2.0 progress Receiving
> objects: 50% (38449/75444), 722.46 MiB | 3.30 MiB/s
> ...
> [INFO] bower ember#2.2.0 progress Receiving
> objects: 99% (75017/75444), 1.56 GiB | 3.31 MiB/s
> Investigate the dependencies and reduce the download size and speed of
> compilation.
> cc/ [~Sreenath] and [~akhilpb]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
