New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 719823 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Proj-Servicification



Sign in to add a comment

Pref service: reduce overhead in startup

Project Member Reported by tibell@chromium.org, May 9 2017

Issue description

As shown in this time breakdown of CreateProfilePrefs

https://docs.google.com/a/chromium.org/spreadsheets/d/1nhLxu71mtj_ZsG5Eo_RXF78OvKxp7ZeEvYtr9zV1ML4/edit?usp=sharing

a lot of time during service startup (which is synchronous) is spent not doing actual work. In particular much time is spent by Mojo (e.g. serialization/deserialization) and some time is spent by the service manager.

We'd like to reduce that overhead.
 
The above profile was generated with these build settings:

target_os = "android"
target_cpu = "arm"
is_debug = false
is_component_build = true
symbol_level = 1
enable_incremental_javac = true
incremental_apk_by_default = true
is_java_debug = true
dcheck_always_on = false
use_goma = true
disable_incremental_isolated_processes=true
is_official_build = false
is_chrome_branded = false

on a Nexus 9.

Comment 2 by tibell@chromium.org, May 16 2017

Components: Internals>Preferences>Service

Comment 3 by tibell@chromium.org, Jun 21 2017

Status: Fixed (was: Untriaged)
We've gotten this down to where it's launchable. Future improvements will likely come from either 1) making Mojo have less overhead in general or 2) make Chrome startup more asynchronous so the service can be started asynchronously with other startup activities.

Sign in to add a comment