Increase the timeout for the perf buildbots.

Increase the timeout for the perf buildbots.

For some reasons, perf slaves link Chrome almost twice slower than a local machine,
and ~1.5 slower than other GCE slaves. Increasing the timeout to remedy the immediate issue.

BUG=chromium:464797
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=298023

[krasin, 2015-12-15 02:13:13]

krasin@google.com changed reviewers:
+ dpranke@google.com

[krasin, 2015-12-15 02:13:14]

The actual link time for Chrome on perf buildbots is 67 minutes. This timeout
also includes some safety margin.

On other buildbots (like the official one) the link time is less than 50
minutes. It's unclear what is different on the perf slaves. That I hope to learn
soon.

[imkrasin, 2015-12-15 04:05:45]

imkrasin@gmail.com changed reviewers:
+ imkrasin@gmail.com

[Alexander Potapenko, 2015-12-15 17:40:12]

glider@chromium.org changed reviewers:
+ glider@chromium.org

[Alexander Potapenko, 2015-12-15 17:40:13]

lgtm

https://codereview.chromium.org/1528533003/diff/1/masters/master.chromium.chr...
File masters/master.chromium.chrome/master.cfg (right):

https://codereview.chromium.org/1528533003/diff/1/masters/master.chromium.chr...
masters/master.chromium.chrome/master.cfg:97: 'factory':
m_annotator.BaseFactory('chromium', timeout=4800),
I'm guessing this is a temporary solution. Can you please link the crbug here,
so that the timeout can be reverted when the bug is fixed?

[krasin, 2015-12-15 17:49:57]

https://codereview.chromium.org/1528533003/diff/1/masters/master.chromium.chr...
File masters/master.chromium.chrome/master.cfg (right):

https://codereview.chromium.org/1528533003/diff/1/masters/master.chromium.chr...
masters/master.chromium.chrome/master.cfg:97: 'factory':
m_annotator.BaseFactory('chromium', timeout=4800),
On 2015/12/15 17:40:13, Alexander Potapenko wrote:
> I'm guessing this is a temporary solution. Can you please link the crbug here,
> so that the timeout can be reverted when the bug is fixed?

Done.

[krasin, 2015-12-15 17:50:02]

The CQ bit was checked by krasin@google.com

[krasin, 2015-12-15 17:50:02]

The patchset sent to the CQ was uploaded after l-g-t-m from glider@chromium.org
Link to the patchset: https://codereview.chromium.org/1528533003/#ps20001
(title: "add TODO")

[commit-bot: I haz the power, 2015-12-15 17:50:11]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1528533003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1528533003/20001

[commit-bot: I haz the power, 2015-12-15 17:52:23]

Description was changed from

==========
Increase the timeout for the perf buildbots.

For some reasons, perf slaves link Chrome almost twice slower than a local
machine,
and ~1.5 slower than other GCE slaves. Increasing the timeout to remedy the
immediate issue.

BUG=chromium:464797
==========

to

==========
Increase the timeout for the perf buildbots.

For some reasons, perf slaves link Chrome almost twice slower than a local
machine,
and ~1.5 slower than other GCE slaves. Increasing the timeout to remedy the
immediate issue.

BUG=chromium:464797

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=298023
==========

[commit-bot: I haz the power, 2015-12-15 17:52:24]

Committed patchset #2 (id:20001) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=298023

[Dirk Pranke, 2015-12-15 23:14:18]

The change lgtm, but the fact that using LTO/CFI causes the link to take 67
minutes (and take 32 GB of ram) is *brutal*. What hope is there for this to be
sped up?

[krasin, 2015-12-15 23:18:58]

On 2015/12/15 23:14:18, Dirk Pranke wrote:
> The change lgtm, but the fact that using LTO/CFI causes the link to take 67
> minutes (and take 32 GB of ram) is *brutal*. What hope is there for this to be
> sped up?

The problem is something to do with the perf slaves.
My local machine links the official Chrome with CFI in 27-28 minutes. Perf
slaves more than 2x slower. More updates are here: https://crbug.com/569732
Such difference is incomprehensible to me. Compute Engine could not be that
slow.