{"id":401,"date":"2022-07-29T07:18:54","date_gmt":"2022-07-29T14:18:54","guid":{"rendered":"https:\/\/blog.mozilla.org\/performance\/?p=401"},"modified":"2023-02-01T03:21:31","modified_gmt":"2023-02-01T11:21:31","slug":"performance-tools-newsletter-h1-2022","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/performance\/2022\/07\/29\/performance-tools-newsletter-h1-2022\/","title":{"rendered":"Performance Tools Newsletter (H1 2022)"},"content":{"rendered":"

As the Perf-Tools team, we are responsible for the Firefox Profiler<\/a>. This newsletter gives an overview of the new features and improvements we\u2019ve done in the first half of 2022.<\/p>\n

You can find the previous newsletter here<\/a> which was about the Q4 2021. This newsletter contains updates related to work done in the first half of 2022.<\/p>\n

Here are some highlights.<\/p>\n

Documentation<\/h2>\n

The main Profiler documentation was refreshed, to better match what has changed in recent years.<\/p>\n

If you are new to the Profiler, or if you would like your friends, colleagues, or customers to learn about it, please visit: https:\/\/profiler.firefox.com\/docs\/#\/.\/guide-getting-started<\/a>.
\n(This link is also accessible from the landing page at https:\/\/profiler.firefox.com<\/a>.)
\n\"Screenshot<\/p>\n

As a reminder, other aspects of the Profiler are captured in separate locations:<\/p>\n

For developers of the Firefox application, or if you are just interested in some technical details, see the internal documentation at https:\/\/firefox-source-docs.mozilla.org\/tools\/profiler\/<\/a>.<\/p>\n

For web developers, one point of interest is that you can add “markers” to your own pages through the JavaScript User Timing API<\/a>, which will then be visible in profiles. This can be useful to measure some specific actions in your web pages.<\/p>\n

Finally, the GitHub repository for the front-end side of the Profiler (the website that actually displays profiles after they have been captured) contains some detailed documentation<\/a> about profile file formats and inner workings of the website.<\/p>\n

New DevTools performance panel<\/h2>\n

The new performance panel was released in Firefox 98. This panel makes it easier for web developers to record and share profiles, as it opens a new profiler.firefox.com tab after capturing the profile.
\n\"Screenshot<\/p>\n

To access it, open the DevTools (main menu > More tools > Web Developer Tools), and select the “Performance” panel.<\/p>\n

Note that having the DevTools open may use some processing power, so the resulting profile of any web page may be slightly skewed, with some of the profile data being related to DevTools. If these effects are noticeable in your profiles, just close the DevTools window while profiling. As an alternative, you may choose to control the profiler through the toolbar button (enabled when first visiting https:\/\/profiler.firefox.com<\/a>), or the accompanying shortcuts: Ctrl+Shift+1 to start, and Ctrl+Shift+2 to stop.<\/p>\n

Internationalization<\/h2>\n

The profiler.firefox.com interface is now available in languages other than English, and may be changed on the fly from the language picker at the bottom right corner\"ScreenshotYou may request new languages, and contribute, at https:\/\/pontoon.mozilla.org\/projects\/firefox-profiler\/<\/a> after signing in with a Firefox Account.<\/p>\n

Markers<\/h2>\n

A number of improvements happened around markers: how they’re collected, some new useful markers that were added around Firefox, and how they are better presented.<\/p>\n