Hotlist Slow: Adopt ChromeOS Session restore tab loading timeouts.

Hotlist Slow: Adopt ChromeOS Session restore tab loading timeouts.

1. Changes desktop tab load time from 100ms to 1500ms.
2. Doesn't preload tabs if network is down.

In my manual testing, the ChromeOS 1500ms timeout does not feel slow.
It actually feels "just right".

BUG=463567
Committed: https://crrev.com/7eb9be569e9e4584624d1617a84d3cc57ea6d8ba
Cr-Commit-Position: refs/heads/master@{#319547}

[tommycli, 2015-03-06 22:44:33]

tommycli@chromium.org changed reviewers:
+ skuhne@chromium.org, thestig@chromium.org

[tommycli, 2015-03-06 22:46:07]

skuhne, thestig: PTAL for bug reporter and OWNER, respectively.

This patch is just a straight copy of the ChromeOS implementation into all OSes.

It works well in my manual testing, and I think the 'network connection'
precondition for tab loading is a good thing for all OSes.

This is not behind a flag, because I think this change is fairly
uncontroversial, and devs can tweak the constant easily for manual testing.

[Mr4D (OOO till 08-26), 2015-03-06 22:59:16]

lgtm

[Lei Zhang, 2015-03-06 23:06:22]

lgtm

[tommycli, 2015-03-06 23:16:32]

skuhne, thestig: thanks for ridiculously fast reviews

[tommycli, 2015-03-06 23:16:37]

The CQ bit was checked by tommycli@chromium.org

[commit-bot: I haz the power, 2015-03-06 23:18:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/983223002/1

[commit-bot: I haz the power, 2015-03-07 01:43:53]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-03-07 01:43:54]

Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_TIMED_OUT, no build
URL)
Timed out jobs are not retried to avoid causing additional load on the builders
with large pending queues.

[Lei Zhang, 2015-03-07 03:03:53]

The CQ bit was checked by thestig@chromium.org

[commit-bot: I haz the power, 2015-03-07 03:05:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/983223002/1

[commit-bot: I haz the power, 2015-03-07 03:06:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-07 03:06:58]

Patchset 1 (id:??) landed as
https://crrev.com/7eb9be569e9e4584624d1617a84d3cc57ea6d8ba
Cr-Commit-Position: refs/heads/master@{#319547}

[chrisha, 2015-03-10 16:41:53]

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

[chrisha, 2015-03-10 16:41:53]

Drive by:

Is it worth wrapping this in a Finch experiment, and actually exploring for the
best value? Do we have key metrics that we can track to quantify the impact? If
not, can we add them?

[tommycli, 2015-03-18 18:45:22]

On 2015/03/10 16:41:53, chrisha wrote:
> Drive by:
> 
> Is it worth wrapping this in a Finch experiment, and actually exploring for
the
> best value? Do we have key metrics that we can track to quantify the impact?
If
> not, can we add them?

Hi chrisha:

On this thread we discuss the metrics showing reduced CPU usage:
https://groups.google.com/a/google.com/d/msg/chrome-fast/0Ly9H-un8WY/5ok8Ctn5...