WebView Startup Optimisation

[Abhijith Nair]

Hi folks,

Hope you are doing great! :)

I am Abhijith and I work on the WebView team. Currently our team is working on improving WebView's startup latency with a strong focus on GMA and AGA. Startup is a big pain point at the moment - p99 is 4 seconds and we don't even record the latency for apps which were killed due to ANR. We need to run startup for every single app individually so that's a lot of start ups we well.

One idea that is being discussed to reduce the latency of startup is to selectively disable certain features, defer them or do them lazily. Since most of the time is spent on //content startup, I wanted to reach out to you folks to get your thoughts.

My questions are:

1/ Do we have prior art for this? 

2/ Do you have pointers on how we can approach this?

3/ Do you have a list of features that we could start with?

4/ I see a minimal browser mode in content initialization, would it be useful for us maybe as a starting point?

5/ Who do you suggest is the right PoC in Chromium for this?

It would be great to hear your thoughts! Thanks!

Best,

Abhijith

--

Abhijith Nair |

Software Engineer |

abhijithnair@google.com

[Stefan Zager]

//content is pretty complicated, and it encompasses a large portion of the overall functionality of chromium, especially if you're counting execution time. My best (and only) suggestion is to generate profiling data to identify bottlenecks. Otherwise, I fear you'll be groping around in the dark in an extremely complex maze.

--
You received this message because you are subscribed to the Google Groups "content-owners" group.
To unsubscribe from this group and stop receiving emails from it, send an email to content-owner...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/content-owners/CADpELh9-pOFALkgJ_Zp3uu_en-S3eE%2BWp-DFoygCVYbbo5fiVg%40mail.gmail.com.