Layout inflation happens on UI thread during activity onCreate |
|
Issue descriptionLayout inflation takes about 200-300ms on lower end devices. It is currently done during oncreate way early during startup. It is however not actually needed until much later (initializeCompositor step). Inflating the layout in a background task should improve startup performance.
,
Apr 11 2018
We don't need fake layout for WebApks though, because there is a splash screen. I think we need to land support for inflating ChromeActivity layout in the background, and then use that in WebApps.
,
Apr 11 2018
Good point, I no longer do any fake layout for WebAppActivity and setContentView is now much faster (4ms) however AsyncInitializationActivity is still taking the same amount of time. I am not sure where it is going now. Current CL here: cl/1008405
,
Apr 11 2018
After some tracing, WebappActivity.initializeWebappData takes 8ms if a fake layout is inflated but 120ms if no fake layout is inflated. Most of the time is spent idle/blocking.
,
Apr 11 2018
In WebappActivity.initializeWebappData, findViewById(android.R.id.content) takes 86ms if no fake layout is set. |
|
►
Sign in to add a comment |
|
Comment 1 by mheikal@chromium.org
, Apr 11 201810.5 MB
10.5 MB View Download
11.5 MB
11.5 MB View Download