{"id":160,"date":"2021-07-15T05:08:05","date_gmt":"2021-07-15T12:08:05","guid":{"rendered":"https:\/\/blog.mozilla.org\/performance\/?p=160"},"modified":"2021-07-15T05:08:05","modified_gmt":"2021-07-15T12:08:05","slug":"whats-new-in-perfherder-2","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/performance\/2021\/07\/15\/whats-new-in-perfherder-2\/","title":{"rendered":"What\u2019s new in Perfherder?"},"content":{"rendered":"

Since last “What’s new in Perfherder” article a lot has changed. Our development team is making progresses towards automating the regression detection process. This post will cover the various improvements that have been made to Perfherder since July 2020.<\/p>\n

Alerts view<\/h3>\n

We added tags for tests. They are meant to describe what type of test it is. For example, the alert below is the PerceptualSpeedIndex<\/span> visual<\/strong> metric for the cold<\/strong> variant of reddit.<\/span><\/p>\n

\"Alert\"

The “Tags” column is next to “Test and platform”<\/p><\/div>\n

We improved the checkbox of the alert summaries so can all alert items be selected by a specific status.<\/p>\n

\"Check

Check alerts menu<\/p><\/div>\n

Talos tests now have links to documentation for every alert item, so if one isn’t very familiar to the regressed\/improved test, this documentation can help for a better understanding of it. The alert items can be sorted by the various columns present in the alerts view. We split the Test and platform <\/strong>column into Test<\/strong> and Platform<\/strong> and we are now able to sort by platform also.<\/p>\n

The Previous Value<\/strong>, New<\/strong> Value<\/strong>, Absolute Difference<\/strong>, and Magnitude of Change <\/strong>were joined together into a single Magnitude of Change<\/strong> column as they were showing basically the same information. Last but not least, the graph link at the end of each test name was moved under the star as a graph icon.<\/p>\n

\"Alerts

The documentation link is present at the end of every test name and platform The sorting buttons are available next to each column<\/p><\/div>\n

Regression template<\/h3>\n

We’ve almost automated the filing of the regression bugs. We don’t have to copy-paste anymore the details from the regressor bug but just to input its number in the dialog below and the new bug screen the fields will auto-populate. The only thing that’s left to be automated is setting the Version<\/strong> of the bug, which should be the latest release of Firefox. It is currently set to unspecified<\/em>.<\/p>\n

\"File

File Regression Bug Modal<\/p><\/div>\n

 <\/p>\n

\"The

The autofilled fields, Screen 1<\/p><\/div>\n

\"The

The autofilled fields, Screen 2<\/p><\/div>\n

\"The

The autofilled fields, Screen 3<\/p><\/div>\n

Another cool thing that we improved is a link to the visual recordings of a browsertime pageload test. In the comment 0\/description of the bug, the old and new (regressed) values are linked to a tgz archive that contains the video recording of the pageload test for each page cycle.<\/p>\n

\"Before

The before and after links are under “Absolute values” column<\/p><\/div>\n

Compare view<\/h3>\n

We added pagination for compare view when the number of results is higher than 10 and now we don’t have the problem of loading too much results in one page anymore.<\/p>\n

\"Compare

Compare view with pagination<\/p><\/div>\n

Backfill tool<\/h3>\n

The backfill tool is probably the biggest surprise. We call it Sherlock. It runs every hour and checks that there are data points for the revision the alert is created on and the previous one. It basically makes sure that there’s no data points gap so the culprit is identified precisely.<\/p>\n

\"Backfill

Backfill report email<\/p><\/div>\n

UI\/UX improvements<\/h3>\n

Of course the improvements are not limited to those, we’ve made various backend and front-end cleanups and optimizations not really visible to the UI:<\/p>\n