Performance Testing Newsletter (Q4 Edition)

Welcome to the latest edition of the Performance Testing Newsletter! The PerfTools team empowers engineers with tools to continuously improve the performance of Mozilla products. See below for highlights from the changes made in the last quarter.

This quarter also saw the release of perf.compare! It’s a new tool used for making comparisons between try runs (or other pushes). It is now the default comparison tool used for these comparisons and replaces the Compare View that was in use previously. Congratulations to all the folks involved in making this release happen! Feel free to reach out in #perfcompare on Matrix if there are any questions, feature requests, etc.. Bugs can be filed in Testing :: PerfCompare.

Highlights from Contributors

PerfCompare

• [sumairq] Add date range to time range dropdown in PerfCompare
• [sumairq] Add Tests for SubtestsResultsView Component
• [osujipius] Add the timezone information in some places

Profiler

• [epsio-yuval] Support colored bandwidth and memory tracks in the Firefox Profiler.
• [nisargjhaveri] Allow loading gzipped profiles from more endpoints and Fix loading and error messages for /from-post-message
• [arpit-ayeeee] Added appropriate null check to handle missing unified string optional values
• [kazarmy] Remove “Recording started” line from Profile Info if startTime is 0 and Chrome .cpuprofile importer: Get profile start time from URL (Chrome DevTools UI format)

Perftest

• [myeongjun] Implemented a test finder for perftest tasks in mach try perf

Highlights from Rest of the Team

• [fbilt] Re-enabled Fission variant for Fenix and GeckoView Android
• [aglavic] Added new mobile startup restore tests in CI.
• [aglavic] Startup tests now gather CPU usage measurements
• [kshampur] Added opt builds for mobile performance tests
• [kshampur] Additional documentation on generating profiles in perftests was added (see here)
• [sparky] Now able to use –full for mach try perf alongside –show-all
• [sparky] New bugbot rule added for monitoring perfalert regression resolution changes
• [sparky] Added a bugbot rule to comment/ni on inactive perf alert regressions

Blog Posts ✍️

• Community Spotlight for Myeongjun Go
• Community Spotlight for Mayank Bansal

Contributors

• Myeongjun Go [:myeongjun]
• Mayank Bansal [:mayankleoboy1]
• Sumair Qaisar [:sumairq]
• Yuval Mizrachi [epsio-yuval]
• Nisarg Jhaveri [nisargjhaveri]
• Arpit Jaiswal [arpit-ayeeee]
• Khairul Azhar Kasmiran [kazarmy]
• Pius Osuji [osujipius]

If you have any questions, or are looking to add performance testing for your code component, you can find us in #perftest on Element, or #perf-help on Slack.