Bugzilla

Any change to the platform names will cause a new performance signature and disrupt continuity of our data series. We also use the `extraOptions` to distinguish signatures, so as long as we continue to include `webrender` in `extraOptions` then we'll avoid non-webrender and webrender results becoming muddled if/when the platform name changes.

For software WebRender we use the `webrender-sw` in `extraOptions` rather than a platform suffix, so I don't think that will be an issue.

We won't be able to combine the current non-WebRender with a new platform suffix of `-nonqr` as these will be distinct signatures. That said, I'm not aware of a performance need to track non-WebRender. Do we know how many users will use this configuration?

Any change to the platform names will cause a new performance signature and disrupt continuity of our data series. We also use the `extraOptions` to distinguish signatures, so as long as we continue to include `webrender` in `extraOptions` then we'll avoid non-webrender and webrender results becoming muddled if/when the platform name changes.

For software WebRender we use the `webrender-sw` in `extraOptions` rather than a platform suffix, so I don't think that will be an issue.

We won't be able to combine the current non-WebRender with a new platform suffix of `-noqr` as these will be distinct signatures. That said, I'm not aware of a performance need to track non-WebRender. Do we know how many users will use this configuration?