(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms.
Bug 1543016 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name?
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | | test | subtest | platform | | | |--|--|--|--|--|--| | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | Improvements: | | test | subtest | platform | | | |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression.
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | ⠀ ⠀ Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> <br />Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> <br />Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> Improvements:<br/> | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | <br /> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 | Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> <br> Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> <br>Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> ####Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> #### Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. #### Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> #### Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. ### Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> #### Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name? Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. Perfherder has detected a talos performance regression from push [05ac29094b09d93fa530a55af7e29ff389353306](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=05ac29094b09d93fa530a55af7e29ff389353306). As author of one of the patches included in that push, we need your help to address this regression. ### Regressions: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 6% | perf_reftest_singletons | id-getter-1.html | linux64-shippable | e10s stylo | 371.20 -> 392.47 | | 5% | perf_reftest_singletons | id-getter-4.html | windows10-64-shippable-qr | e10s stylo | 449.85 -> 472.94 | | 5% | perf_reftest_singletons | id-getter-5.html | windows10-64-shippable-qr | e10s stylo | 449.57 -> 472.48 | | 5% | perf_reftest_singletons | id-getter-4.html | linux64-shippable | e10s stylo | 372.43 -> 391.39 | | 5% | perf_reftest_singletons | id-getter-6.html | windows10-64-shippable-qr | e10s stylo | 449.90 -> 472.52 |<br> ### Improvements: | **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| |--|--|--|--|--|--| | 47% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable-qr | e10s stylo | 107.94 -> 57.56 | | 45% | perf_reftest_singletons | getElementById-1.html | windows7-32-shippable | e10s stylo | 109.29 -> 59.60 | | 45% | perf_reftest_singletons | getElementById-1.html | windows10-64-shippable | e10s stylo | 105.75 -> 58.48 | | 42% | perf_reftest_singletons | getElementById-1.html | macosx1014-64-shippable | e10s stylo | 100.85 -> 58.98 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable | e10s stylo | 94.77 -> 56.10 | | 41% | perf_reftest_singletons | getElementById-1.html | linux64-shippable-qr | e10s stylo | 98.22 -> 58.41 | | 12% | dromaeo_dom | | linux64-shippable | e10s stylo | 1,887.73 -> 2,117.95 | Details of the alert can be found in the [alert summary](http://localhost:5000/perf.html#/alerts?id=27129), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #5) > that would be a much larger change, we can file a bug or make this part of that, but I suspect it will be a wontfix or treated low priority. There are a lot of moving parts to consider in making that happen. How is this a problem now and wasn't a problem before? We adapted to the old problems on the fly. For example, it's understandable why we receive **OPT**-like measurements from shippable-configured platforms. But the variation from this case brought some extra confusion for other people reading the dashboards: the fact that we got **OPT**-like measurements *(which are actually PGO)* originating from PGO-enabled platforms. It's an ambiguous situation and a reader wouldn't know which signature part to trust: the build config or the platform name?