https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2017-02-06&keys=__none__!__none__!__none__&max_channel_version=aurora%252F53&measure=CONTENT_PROCESS_LAUNCH_TIME_MS&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2017-01-26&table=0&trim=1&use_submission_date=0
This shows the distribution of times to launch a content process from the time we initially ask for it to the time we get back the first initialization message through IPDL. So this covers actual process launch in the OS, XPCOM startup, and other bootstrap. At first glance, this appears worrying to me: almost 25% of content process startups take more than 1 second, and the median is >700ms. And this is on nightly/aurora, which users typically have faster computers. There's a lot of potential noise here: we don't know what else is going on on the computer (maybe it's near boot and there's still a lot of system churn). But this time definitely can have an impact on how quickly Firefox is ready to load pages and therefore the impression that users have of its total speed. Soliciting everyone's opinion, but Harald's in particular: is it important to dive into this in more detail soon (before Firefox 57)? This metric is currently exploratory, and so I need guidance about whether it's important to keep this metric around for e.g. a release-health dashboard or to prevent regressions. --BDS _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
