New issue
Advanced search Search tips

Issue 634036 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 505677
Owner:
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Renderer warm up

Project Member Reported by smaier@chromium.org, Aug 3 2016

Issue description

We want to investigate the benefits of starting a renderer process before we need one in Android. Starting a new process is costly for us, so this optimization will sidestep the startup time for the new process, while potentially costing us more RAM.

 
Some things I want to investigate:

1) Does reduced renderer startup time actually matter? What evidence is there that shortening the time from request renderer -> connection actually affects the user?
2) Can we make this warmed up renderer process a background process so that it gets killed first?
3) When is the best time to warm up a renderer process?

Some preliminary research is here.

https://docs.google.com/a/chromium.org/document/d/1UfN3YXGe30ZYuk0yZ_BOl1bLeN0V9Sj-7Wj2FxazuYw/edit?usp=sharing
Mergedinto: 505677
Status: Duplicate (was: Untriaged)

Sign in to add a comment