Measure the renderer process startup performance for the case of creating a second webview after the renderer has exited |
|||||||||
Issue descriptionWe measure startup performance currently, but we don't capture the case where all WebViews are destroyed (leading to the renderer exiting) and then create a new WebView. Although doing this is a memory saving, it may also represent a latency regression for applications. We should track this also to ensure that we don't regress from where we are currently.
,
Apr 12 2017
,
Apr 12 2017
,
Apr 12 2017
,
Apr 12 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 16 2018
Changwan, it seems like - given your current focus - this should be assigned to you.
,
Apr 16 2018
,
Apr 16 2018
,
Apr 17 2018
Yes, I noticed this while measuring startup time locally. Usually, startup time was 4x or 5x longer when that happens - I'm not sure how it's reflected in our perfs now, but I think setting such a separate metric would be a good start. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by tobiasjs@chromium.org
, Mar 31 2017