Ever wondered why building Firefox takes so long? You can now visualize the answer!
As of last week, clicking any Firefox build job on treeherder shows a big « Open in Firefox Profiler » grey button. Clicking it opens a profile of the build in a Firefox Profiler tab. The profile contains both a sampling of resource use (CPU, memory, disk I/O) and markers indicating what the build was doing at any time. This makes it really easy to understand which parts of the build were multi-threaded and which parts of the build were not taking advantage of the available cores. For your local builds, after `mach build` finishes, you can run `mach resource-usage` to open a profile in a Firefox tab. Many thanks to glandium who helped me land and polish this over the last few days. Implementation bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1850647 Treeherder link for an example: https://treeherder.mozilla.org/jobs?repo=mozilla-central&revision=a9a0ca5dc9605973d81ded607dfccd4d0a08dc68&selectedTaskRun=KkXYYkhNRyiuplEtG7nZog.0 Direct link to an example profile: https://share.firefox.dev/46BPftW I hope this will help make our builds faster! -- Florian Quèze -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAFu36SrURtoLqckBWszzT1nDNjzOj%3DQuoL8tO%2BaTa6A%2B6D7X%3DA%40mail.gmail.com.
