зеркало из https://github.com/mozilla/gecko-dev.git
42c1262dfd
This patch adds some telemetry histograms: * CONTENT_PROCESS_LAUNCH_IS_SYNC - boolean, true if the content process was launched synchronously (blocking the main thread) * CONTENT_PROCESS_SYNC_LAUNCH_MS - the time consumed by sync launch; the main thread will be busy or blocked for this entire time * CONTENT_PROCESS_LAUNCH_TOTAL_MS - the total time elapsed from the start of async content process launch until the launch promise is resolved and the ContentParent can be sent IPDL messages * CONTENT_PROCESS_LAUNCH_MAINTHREAD_MS - the time consumed on the parent process main thread during async content process launch; typically this is due to ContentParent::Init. * CHILD_PROCESS_LAUNCH_MS - for any kind of Gecko child process (including plugins, GPU, etc.), the time taken in the common process launch code (which is run off-main-thread) The probes restricted to async content process launch don't have "async" in the name because that will eventually become the only kind of content process launch. Depends on D8943 Differential Revision: https://phabricator.services.mozilla.com/D8944 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| app | ||
| chromium | ||
| contentproc | ||
| glue | ||
| ipdl | ||
| mscom | ||
| testshell | ||
| moz.build | ||
| pull-chromium.py | ||