In crbug.com/735799#c16 we can see that startup time decreased to 2641.3 ms with several potential optimizations.

That was on gobo_512 @ OPG1.170814.001 and Chrome @ 4ebc56f91e1af7ae50abd9956fed637b0f4a23e2 (Aug 14).

However, Chrome @ 76b6ed4c81cda89f340495e9443c4c7b5ab93674 (Aug 28) with same optimizations shows startup times around 4 seconds.

See two traces attached. The one from 14th has an issue with tasks not terminating properly, but that doesn't affect startup time measurement.

We can see that things universally got slower:

NAME
14th            28th
-----------------------------------------------------------------

Looper.dispatchMessage: android.app.ActivityThread$H
481.685 ms      894.049 ms

AsyncInitializationActivity.onCreate()
298.180 ms      718.366 ms

(until content::Start)
164             392

content::Start
163.218 ms      128.958 ms

(until the end of ChromeBrowserMainParts::PreMainMessageLoopRun)
558             424

(until ChromeTabbedActivity.initializeState)
355             737

TabModelImpl.setIndex
185.342 ms      343.916 ms

ChromeTabbedActivity.finishNativeInitialization
282.733 ms      778.626 ms

 

Deleted: Chrome28th.html.gz 1.2 MB

Chrome28th.html.gz 1.2 MB Download

Deleted: Chrome14th.html.gz 944 KB

Chrome14th.html.gz 944 KB Download