WebView multiprocess startup time could be improved |
||||
Issue descriptionMaster bug for tracking improvements to WebView startup time in multiprocess mode. Multiprocess startup is currently significantly slower than single-process, and this needs to be reduced for it to become the default behaviour instead of just a developer option.
,
Oct 27 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/53cb8b57b2ba954bbce9fbe0503d127c565b1670 commit 53cb8b57b2ba954bbce9fbe0503d127c565b1670 Author: torne <torne@chromium.org> Date: Thu Oct 06 17:20:07 2016 Prewarm WebView renderer when in multiprocess mode. When we're in multiprocess mode, prewarm the renderer process early in browser startup in the same way Chrome does. This reduces the startup time penalty of multiprocess WebView by almost half in simple local tests on a Nexus 6P. BUG=653560 Review-Url: https://codereview.chromium.org/2390203006 Cr-Commit-Position: refs/heads/master@{#423569} [modify] https://crrev.com/53cb8b57b2ba954bbce9fbe0503d127c565b1670/android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java
,
Nov 4 2016
[Automated comment] removing mislabelled merge-merged-2840
,
Jan 30 2017
The change above and some other changes made on android and chromium sides have improved startup time to the point where it's not a major issue, though there may be more improvements possible in future.
,
Jan 30 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Oct 6 2016